Domain Specific Markup Language Php

How does a DSML help?

Here’s what I want to write:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

<steps> <step> Put your left foot in <tests> <test>Left foot is in front of you</test> <test>Balanced on right foot</test> </tests> </step> <step> Take your left foot out <cli> student@server $ out /dev/left-foot </cli> <tests> <test>Left foot is behind you</test> <test>Balanced on right foot</test> </tests> </step> </steps>

This is starting to look like XML, without accidentally becoming XHTML. The joy of my DSML is that I’m writing a language that knows what I mean, not that I want a new layer of quoting rules.

Rewriting Custom Tags into HTML

Let’s start with the easy work, let’s convert the <steps> list and the <step> elements back into <ol> and <li>s. I’m using the QueryPath library. It’s a very similar API to jQuery, and because I do the transform server-side, I can provide well-formed pages to clients without JavaScript (like search engine spiders).

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

<?php require 'QueryPath/QueryPath.php'; $qp = htmlqp($dsml_file); //The DSML in the previous code block foreach($qp->find(":root steps > step") as $step){ $content = $step->innerHTML(); $step->replaceWith("<li>" . $content . "</li>"); } foreach($qp->find(":root steps:first") as $elm){ $content = $elm->innerHTML(); $elm->replaceWith("<ol id='tests'>" . $content . "</ol>"); } $qp->writeHTML(); ?>

Adding Application Logic and Error Checking

Of course, nobody’s perfect, so let’s add some rules to catch operator error:

1 2 3 4 5 6 7 8 9

<?php if($qp->find(":root steps")){ //We already translated steps:first into an ol warn("You have more than one <steps> collection."); } if($qp->find(":root step")){ //We already translated any step that is a direct child of steps warn("You have <step> elements outside of the <steps> container."); } ?>

While I’m writing lessons, my warn() function adds bold red error messages to the top of the parsed document. In production, warn() will quietly log them.

Tags that are Smarter than HTML

Those were simple replacements, you can do that with a regular expression and some duck tape. Let’s make this <cli> tag fix my problems with HTML’s <pre>:

• I want to be able to indent the content for easier editing.
• I want the </pre> tag on its own line, without showing the student an empty line at the bottom of the code block.

In other words, I want it to work like this:

1 2 3 4

<li> <pre class='cli'> student@server $ out /dev/left-foot</pre> </li>

But let me edit it like this:

1 2 3 4 5

<li> <cli> student@server $ out /dev/left-foot </cli> </li>

Here’s the code that does it:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

<?php foreach($qp->find(":root cli") as $elm){ $content = $elm->innerHTML(); //Accept Windows or Unixy EOL $content_array = preg_split('/(\r\n|\r|\n)/', $content); //Get rid of whitespace on left and right. $content_array = array_map("trim", $content_array); //Get rid of trailing empty lines while(end($content_array) == ""){ array_pop($content_array); } //Reassemble with uniform EOL $content = implode("\r\n", $content_array); $elm->replaceWith("<pre class='console'>" . $content . "</pre>"); } ?>

DSML my Users Care About

In lessons, when we introduce new terms, the student can hover over them to get a Bootstrap Popover that loads the definition from our glossary, dynamically. Here’s how that used to look in our code:

1 2 3

Now edit my.cnf: <pre> $ <abbr href='/glossary/sudoedit'>sudoedit</abbr> /etc/my.cnf</pre>

Here’s how I want it to look:

1 2 3 4

Now edit my.cnf: <cli> $ <explain>sudoedit</explain> /etc/my.cnf </cli>

And here’s how we do it:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

<?php function term_to_url($title){ $title = strtolower($title); $title = preg_replace('/[ \t\r\n]+/', '-', $title); $title = preg_replace('/[^a-z0-9\-_]/', '', $title); return $title; } foreach($qp->find(":root explain") as $elm){ $content = $elm->innerHTML(); $url = '/glossary/' . term_to_url($elm->text()); if(file_exists('..' . $url)){ $elm->replaceWith("<abbr href='$url'>" . $content . "</abbr>"); }else{ warn("No glossary entry for $url"); $elm->replaceWith($content); } } ?>

Now we get warnings about terms we haven’t written glossary entries for (and we don’t call attention to them, to avoid embarrassment in front of students). Tagging glossary entries is easier (so we’ll do it more). And we’re free to make dramatic changes to the way we present glossary terms without touching a zillion lesson files. For example:

• We could slipstream in all the definitions into data attributes instead of fetching via AJAX.
• We could paste all the definitions as numbered footnotes on the page.
• We could switch the HTML we emit to the browser to use the <dfn> tag instead of <abbr>.

Now go forth, and HTML no more.

HTML is pretty great, but I wouldn’t want to write in it.

• A DSML can get you closer to your problem domain, not just in code, but in presentation.
• A DSML can free you to write content without bogging you down in implementation details.
• A DSML can even make it easier to develop and update features spread across content.

Original Post:  Jeremy Wadhams Mar 18th, 2013
http://www.wingtiplabs.com/blog/posts/2013/03/18/domain-specific-markup-language/
https://docs.google.com/file/d/0B5nZNPW48dpFUTI1Mi1qZWhVVkE/edit?usp=sharing 

Php Custom Tag Library

Right now I'm leaning towards the Custom Tags library. One of the best features is support for buried or nested tags like the code block below:

<?php
$current_dir = dirname(__FILE__) . DIRECTORY_SEPARATOR;
require_once $current_dir . 'customtags.php'; 
$ct = new CustomTags(array(
    'parse_on_shutdown' => true,
    'tag_directory' => $current_dir . 'tags' . DIRECTORY_SEPARATOR,
    'sniff_for_buried_tags' => true 
)); 
?> 

<ct:header example_name="Simple Example">Going Well?</ct:header>

Download php tag library from here
or go to
https://github.com/buggedcom/PHP-Custom-Tags

Enable SSL in Apache Server in Windows

Step 1: Installing OpenSSL on Windows

Step 2: Create Self-Signed Certificate Windows 

Step 3: Open up conf\httpd.conf in a text editor and look for the line LoadModule ssl_module modules/mod_ssl.so and remove any pound sign (#) characters preceding it. If you don't see that line where it probably should be (among the other LoadModule lines), then your installation may not have mod_ssl.so ... can't help you there!

 

Step 4. Also, while you're in conf\httpd.conf, make sure the following lines exist somewhere:

 <IfModule mod_ssl.c>
     Include conf/ssl.conf
 </IfModule>

Step 5. Create a directory under conf called ssl and copy the cp.key (your key file) and cp.cert (your certificate file) files there.

Step 6. Create a file conf\ssl.conf and open in a text editor and paste the following code:

<IfModule ssl_module>
# Pseudo Random Number Generator (PRNG):
# Configure one or more sources to seed the PRNG of the SSL library.
# The seed data should be of good random quality.
# WARNING! On some platforms /dev/random blocks if not enough entropy
# is available. This means you then cannot use the /dev/random device
# because it would lead to very long connection times (as long as
# it requires to make more entropy available). But usually those
# platforms additionally provide a /dev/urandom device which doesn't
# block. So, if available, use this one instead. Read the mod_ssl User
# Manual for more details.

#SSLRandomSeed startup file:/dev/random  512
#SSLRandomSeed startup file:/dev/urandom 512
#SSLRandomSeed connect file:/dev/random  512
#SSLRandomSeed connect file:/dev/urandom 512

# When we also provide SSL we have to listen to the
# standard HTTP port (see above) and to the HTTPS port
#
# Note: Configurations that use IPv6 but not IPv4-mapped addresses need two
#       Listen directives: "Listen [::]:443" and "Listen 0.0.0.0:443"
#
#Listen 0.0.0.0:443
#Listen [::]:443
Listen 443

##  SSL Global Context
##
##  All SSL configuration in this context applies both to
##  the main server and all SSL-enabled virtual hosts.

<IfModule mime_module>
    #
    #   Some MIME-types for downloading Certificates and CRLs
    #
    AddType application/x-x509-ca-cert .crt
    AddType application/x-pkcs7-crl    .crl
</IfModule>

#   Pass Phrase Dialog:
#   Configure the pass phrase gathering process.
#   The filtering dialog program (`builtin' is a internal
#   terminal dialog) has to provide the pass phrase on stdout.
SSLPassPhraseDialog  builtin

#   Inter-Process Session Cache:
#   Configure the SSL Session Cache: First the mechanism
#   to use and second the expiring timeout (in seconds).
#SSLSessionCache         "dbm:logs/ssl.scache"
##SSLSessionCache        "shmcb:logs/ssl.scache(512000)"
##SSLSessionCacheTimeout  300

#   Semaphore:
#   Configure the path to the mutual exclusion semaphore the
#   SSL engine uses internally for inter-process synchronization.
SSLMutex default

##
## SSL Virtual Host Context
##

<VirtualHost *:443>
    #   General setup for the virtual host
    ## location where your documents are exists
    DocumentRoot "C:/xampp/htdocs/contactwebspace/app2"

    ## server name you used to create you certificate
    ## and make sure a entry in "C:\Windows\System32\drivers\etc\hosts"
    ## like: 127.0.0.1 pritom.com
    ## and : 127.0.0.1 www.pritom.com
    ServerName pritom.com:443
    ServerAlias www.pritom.com:443
    ServerAdmin webmaster@localhost
    ErrorLog "logs/error-ssl.log"
    <IfModule log_config_module>
        CustomLog "logs/access-ssl.log" combined
    </IfModule>
  
    #   SSL Engine Switch:
    #   Enable/Disable SSL for this virtual host.
    SSLEngine on
  
    #   SSL Cipher Suite:
    #   List the ciphers that the client is permitted to negotiate.
    #   See the mod_ssl documentation for a complete list.
    SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
  
    #   Server Certificate:
    #   Point SSLCertificateFile at a PEM encoded certificate.  If
    #   the certificate is encrypted, then you will be prompted for a
    #   pass phrase.  Note that a kill -HUP will prompt again.  Keep
    #   in mind that if you have both an RSA and a DSA certificate you
    #   can configure both in parallel (to also allow the use of DSA
    #   ciphers, etc.)
    #SSLCertificateFile "conf/ssl.crt/server-dsa.crt"
    #SSLCertificateFile "conf/ssl.crt/server.crt"
    SSLCertificateFile "conf/ssl/cp.cert"
  
    #   Server Private Key:
    #   If the key is not combined with the certificate, use this
    #   directive to point at the key file.  Keep in mind that if
    #   you've both a RSA and a DSA private key you can configure
    #   both in parallel (to also allow the use of DSA ciphers, etc.)
    #SSLCertificateKeyFile "conf/ssl.key/server-dsa.key"
    #SSLCertificateKeyFile "conf/ssl.key/server.key"
    SSLCertificateKeyFile "conf/ssl/cp.key"
  
    #   Server Certificate Chain:
    #   Point SSLCertificateChainFile at a file containing the
    #   concatenation of PEM encoded CA certificates which form the
    #   certificate chain for the server certificate. Alternatively
    #   the referenced file can be the same as SSLCertificateFile
    #   when the CA certificates are directly appended to the server
    #   certificate for convinience.
    #SSLCertificateChainFile "conf/ssl.crt/server-ca.crt"
  
    #   Certificate Authority (CA):
    #   Set the CA certificate verification path where to find CA
    #   certificates for client authentication or alternatively one
    #   huge file containing all of them (file must be PEM encoded)
    #   Note: Inside SSLCACertificatePath you need hash symlinks
    #         to point to the certificate files. Use the provided
    #         Makefile to update the hash symlinks after changes.
    #SSLCACertificatePath "conf/ssl.crt"
    #SSLCACertificateFile "conf/ssl.crt/ca-bundle.crt"
  
    #   Certificate Revocation Lists (CRL):
    #   Set the CA revocation path where to find CA CRLs for client
    #   authentication or alternatively one huge file containing all
    #   of them (file must be PEM encoded)
    #   Note: Inside SSLCARevocationPath you need hash symlinks
    #         to point to the certificate files. Use the provided
    #         Makefile to update the hash symlinks after changes.
    #SSLCARevocationPath "conf/ssl.crl"
    #SSLCARevocationFile "conf/ssl.crl/ca-bundle.crl"
  
    #   Client Authentication (Type):
    #   Client certificate verification type and depth.  Types are
    #   none, optional, require and optional_no_ca.  Depth is a
    #   number which specifies how deeply to verify the certificate
    #   issuer chain before deciding the certificate is not valid.
    #SSLVerifyClient require
    #SSLVerifyDepth  10
  
    #   Access Control:
    #   With SSLRequire you can do per-directory access control based
    #   on arbitrary complex boolean expressions containing server
    #   variable checks and other lookup directives.  The syntax is a
    #   mixture between C and Perl.  See the mod_ssl documentation
    #   for more details.
    #<Location />
    #SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
    #  and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
    #  and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
    #  and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
    #  and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20       ) \
    #  or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
    #</Location>
  
    #   SSL Engine Options:
    #   Set various options for the SSL engine.
    #   o FakeBasicAuth:
    #     Translate the client X.509 into a Basic Authorisation.  This means that
    #     the standard Auth/DBMAuth methods can be used for access control.  The
    #     user name is the `one line' version of the client's X.509 certificate.
    #     Note that no password is obtained from the user. Every entry in the user
    #     file needs this password: `xxj31ZMTZzkVA'.
    #   o ExportCertData:
    #     This exports two additional environment variables: SSL_CLIENT_CERT and
    #     SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
    #     server (always existing) and the client (only existing when client
    #     authentication is used). This can be used to import the certificates
    #     into CGI scripts.
    #   o StdEnvVars:
    #     This exports the standard SSL/TLS related `SSL_*' environment variables.
    #     Per default this exportation is switched off for performance reasons,
    #     because the extraction step is an expensive operation and is usually
    #     useless for serving static content. So one usually enables the
    #     exportation for CGI and SSI requests only.
    #   o StrictRequire:
    #     This denies access when "SSLRequireSSL" or "SSLRequire" applied even
    #     under a "Satisfy any" situation, i.e. when it applies access is denied
    #     and no other module can change it.
    #   o OptRenegotiate:
    #     This enables optimized SSL connection renegotiation handling when SSL
    #     directives are used in per-directory context.
    #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
    <FilesMatch "\.(cgi|shtml|pl|asp|php)$">
        SSLOptions +StdEnvVars
    </FilesMatch>
    <Directory "C:/xampp/cgi-bin">
        SSLOptions +StdEnvVars
    </Directory>
  
    #   SSL Protocol Adjustments:
    #   The safe and default but still SSL/TLS standard compliant shutdown
    #   approach is that mod_ssl sends the close notify alert but doesn't wait for
    #   the close notify alert from client. When you need a different shutdown
    #   approach you can use one of the following variables:
    #   o ssl-unclean-shutdown:
    #     This forces an unclean shutdown when the connection is closed, i.e. no
    #     SSL close notify alert is send or allowed to received.  This violates
    #     the SSL/TLS standard but is needed for some brain-dead browsers. Use
    #     this when you receive I/O errors because of the standard approach where
    #     mod_ssl sends the close notify alert.
    #   o ssl-accurate-shutdown:
    #     This forces an accurate shutdown when the connection is closed, i.e. a
    #     SSL close notify alert is send and mod_ssl waits for the close notify
    #     alert of the client. This is 100% SSL/TLS standard compliant, but in
    #     practice often causes hanging connections with brain-dead browsers. Use
    #     this only for browsers where you know that their SSL implementation
    #     works correctly.
    #   Notice: Most problems of broken clients are also related to the HTTP
    #   keep-alive facility, so you usually additionally want to disable
    #   keep-alive for those clients, too. Use variable "nokeepalive" for this.
    #   Similarly, one has to force some clients to use HTTP/1.0 to workaround
    #   their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
    #   "force-response-1.0" for this.
    BrowserMatch ".*MSIE.*" nokeepalive ssl-unclean-shutdown downgrade-1.0 force-response-1.0
  
    #   Per-Server Logging:
    #   The home of a custom SSL log file. Use this when you want a
    #   compact non-error SSL logfile on a virtual host basis.
    CustomLog "logs/ssl_request.log" "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
</VirtualHost>                                
</IfModule>

Step 7: If you maintain any virtual host file make sure there are not entry like:
NameVirtualHost *

Make the line seems to be like the following:
NameVirtualHost *:80

If virtual host file contains any block as:
<VirtualHost *>

Change it to:
<VirtualHost *:80>

for support non ssl (port: 80) as http request. 

Step 8: Restart your apache server.

Step 10: Hit browser with the following url: https://pritom.com (as you used this web address in your ssl.conf file and has a entry in host file)

Create Self-Signed Certificate Windows

At first install OpenSSL in your windows machine.

Several files related to your your SSL certificate will be created in this section, so choose a common base name to use. In my examples I use "blarg", which I've italicised to show it should be replaced by your choice. In practice, I recommend extracting the essence from your domain name; for example, if I was creating a certificate for https://www.neilstuff.com/ then I'd use "neilstuff".

Open up a command prompt and go to the directory where you unzipped OpenSSL and run the following command to create a new certificate request:

openssl req -config openssl.cnf -new -out blarg.csr -keyout blarg.pem

You'll be prompted to answer many questions, which ones depend on your openssl.cnf file; all except two of these can be left blank:

• PEM pass phrase: Password associated with the private key (blarg.pem) you're generating. Since we'll be removing this for the benefit of Apache 2.0.X, I suggest using something like "none" or "password".
• Common Name: The fully-qualified domain name associated with this certificate. In my example, I use www.blarg.com which means I damn well better use that certificate on https://www.blarg.com/. For personal security, testing, or intranets it's okay for this to not quite match -- just be prepared to deal with warnings from web browsers and such.

Now it's time to create a non-password protected key for Apache 2.0.X by executing the following:

openssl rsa -in blarg.pem -out blarg.key

The only thing you'll be asked is the password you had used. Your resulting KEY file is essential the same thing as the PEM, just not password protected.

Before we go on, delete the .rnd file. This contains entropy information which could be used by malicious people to try and crack your certificate later on (if they get a hold of it).

Finally, run the following command to create an X.509 certificate, e.g. the kind of certificate that SSL likes to munch:

openssl x509 -in blarg.csr -out blarg.cert -req -signkey blarg.key -days 365

 

Congratulations, you've created a self-signed certificate! Keep the KEY and CERT files some place safe, we'll be using them soon.

Installing OpenSSL on Windows

OpenSSL is officially distributed in C source code format. This is not a problem for Unix systems where C compiler is always available. But if you have a Windows system, you will have a hard time to install OpenSSL in C source code format. What you should do is to find a pre-compiled binary version for Windows. Here is my sugge I installed OpenSSL on my Windows system: 

1. Go to http://gnuwin32.sourceforge.net/packages/openssl.htm, and download the "Zip" version. 

2. Unzip the file somewhere on your computer. 

3. Copy all the libeay32.dll and ssleay32.dll to your Windows\System32 or xampp/php (if you are using xampp server) directory. If you've dealt with SSL at all before, especially as a developer, you might already have copies of these there. Keep whatever is newest.

4. Open command line window, and try the following command: 

Code:

>\local\gnuwin32\bin\openssl -help
openssl:Error: '-help' is an invalid command.

Standard commands
asn1parse      ca             ciphers        crl            crl2pkcs7
dgst           dh             dhparam        dsa            dsaparam
enc            engine         errstr         gendh          gendsa
genrsa         nseq           ocsp           passwd         pkcs12
pkcs7          pkcs8          rand           req            rsa
rsautl         s_client       s_server       s_time         sess_id
smime          speed          spkac          verify         version
x509
......

5. You'll also need an openssl.cnf which is an OpenSSL configuration file that, for some reason, doesn't come with Hunter's distribution. Download this one or this one or this one or this one and save it to the folder where you unzipped OpenSSL.

If you see the list of commands printed by OpenSSL, you know that your installation is done correctly.

------------ 
For other tutorials on OpenSSL, see http://www.herongyang.com/crypto/

__________________
Good tutorials for beginners on PHP, JSP, ASP, SQL, ... 
--> http://www.herongyang.com/

Download openssl as zip file from here

http://forums.tutorialized.com/windows-122/openssl-installation-on-windows-tutorial-by-herong-5467.html