Browser Info
Often important in web development is to establish the browser information so that customised code can be targeted to certain browsers. The information gained can also be used to exclude some visitors based on their ip address or redirect browsers based on their connection method.
[browsername] tag
Example WebDNA code:
[browsername][ipaddress] tag
Alternatively, [realip] displays the ip address without expanding to 3 digits per segment of the remote computer.
Example WebDNA code:
[ipaddress] [realip] WebDNA v8.1+ tag
Example WebDNA code:
[realip] [referrer] tag
Example WebDNA code:
[referrer]This will not work if the previous page was a form using post, ie: <form method="post">
[httpmethod] tag
Example WebDNA code:
[httpmethod][thisfile] tag
Example WebDNA code:
[thisfile][thishost] tag
Example WebDNA code:
[thishost][thisport] tag
Example WebDNA code:
[thisport][thisurl] tag
Example WebDNA code:
[thisurl]When used on a page such as http://www.domain.com/x/y/z/index.dna?a=b&c=d [thisurl] will return /x/y/z/index.dna, note the return stops at the ?
If the variables from a url are also required such as a and c from this url:
http://www.domain.com/x/y/z/index.dna?a=b&c=d then use [thisurlplusget]
[thisurl] when writing "Pretty URLs" using .htaccess
When writing "pretty urls" using .htaccess [thisurl] will NOT return the rewritten url, however there is a workaround if the "requested URL" is required.
Example:
# This rule is to manage products when URL = http://domain.com/department/[DEPT-URL]
# Example: http://domain.com/department/clothing
RewriteRule ^department/([a-z,0-9\_\-]+)$ /department-display.dna\?d=$1 [NC,L]
In this example the results of a "department" are displayed using this URL http://domain.com/department/clothing, then using RewriteRule the required data can be displayed by sending the DEPT-URL to be processed by /department-display.dna\?d=$1.
This may not be ideal if you want to use the requested URL for further navigation as [thisurl] will return "/department-display.dna" or "/department-display.dna?d=clothing" if using [thisurlplusget].
By capturing the request_uri and passing the value as a variable to the WebDNA page simpley add it as a variable to the end of the rewrite string:
/department-display.dna\?d=$1&varREQUESTSTRING=%{request_uri} << note this is uri not url
Now on the WebDNA page:
varREQUESTSTRING = [varREQUESTSTRING] will display the original requested string as:
varREQUESTSTRING = /department/clothing
[thisurlplusget] tag
Example WebDNA code:
[thisurlplusget][setmimeheader] tag
Example WebDNA code:
[setmimeheader name=Content-Type&value=text/html; charset=iso-8859-1]Parameters
| Parameter | Description |
|---|---|
| Name | The name of the MIME header to set. |
| Value | The value of the MIME header being set. |
[getmimeheader] WebDNA v6.0+ tag
Example WebDNA code:
[getmimeheader name=HTTP_ACCEPT_LANGUAGE]Parameters
| Parameter | Description |
|---|---|
| Name | The name of the MIME header to list. |
| Exact | T(rue) or F(alse) whether to exactly match the name of the parameter or match any name that contains the "name" value. (Default value is true.) |
[listmimeheaders] context
Parameters
| Parameter | Description |
|---|---|
| Name | The name of the MIME header to list. |
| Exact | T(rue) or F(alse) whether to exactly match the name of the parameter or match any name that contains the "name" value. (Default value is true.) |
Tags available inside a [listmimeheaders] context:
| Tag | Description |
|---|---|
| [index] | A number indicating this mime header's placement in the list |
| [name] | The name of the mime header |
| [value] | The value associated with the mime header |
[listmimeheaders]
[index] [name] [value]<br>
[/listmimeheaders]
Example WebDNA code:
[listmimeheaders name=HTTP_HOST&exact=t]
[value]
[/listmimeheaders]
[returnraw] WebDNA v8.6.5 context
To get more control over the exact MIME header information sent to the browser, place a [returnraw] context into a template. You can create 'true' URL-redirect pages this way, or use it to force the remote browser to display password dialogs. Probably the most common use for this feature is to create "click-through" statistics on pages where you place advertisements with hyperlinks leading away from your site. ReturnRaw allows you to insert some WebDNA (to increment a hit counter, for instance) before leading the customer away from your site.
Example WebDNA code:
[returnraw]HTTP/1.0 200 OK
Content-type: text/html[unurl]%0D%0A%0D%0A[/unurl]
<html>
...your HTML here...
</html>[/returnraw]the above example must have several <Carriage Return><LineFeed> at the end of the line in order to work. On a PC, simply using NotePad to create the file will put CR/LF in the proper places. On a Macintosh you may use BBEdit or another text editor to set the file type to DOS-style line endings.
For illustration purposes, the example above shows the MIME headers automatically created for you whenever you display any normal page from WebDNA. Of course, since these headers are always created automatically, this example does nothing special -- the real usefulness of this feature comes when you change the MIME headers to do something special, like a URL-redirect.
The following example causes the remote browser to immediately redirect to a different URL. This is better that the META tag some newer browsers support, because almost all browsers understand the low-level MIME header URL redirect.
[returnraw]HTTP/1.0 302 Found
Location: http://www.webdna.us/[unurl]%0D%0A%0D%0A[/unurl]
(some WebDNA here that does something interesting)
[/returnraw][returnraw]HTTP/1.1 301 Moved Permanently
Location: http://www.webdna.us[unurl]%0D%0A%0D%0A[/unurl][/returnraw]when you put a [returnraw] context into a template, any text outside the [ReturnRaw] container is ignored. So if you want to display some HTML after the raw MIME headers, you must put that HTML inside the context.
'BinaryBody' option:
[returnraw binarybody=...]
Allows the WebDNA programmer to designate a file (binary or text) to be attached as the 'body' of an HTTP response. This makes it possible to send a binary file (image, executable, etc...) back to the client. For example, you can create download links for any type of file, and that would force the 'save as' dialog to open on the client machine.
Example code: Creates a download link for every file in the current folder, binary or text.
<!--HAS_WEBDNA_TAGS-->
<HTML>
<BODY>
[!]Initailize the getfile variable[/!]
[text secure=f]getfile=[/text]
[!]Check if filename was passed in[/!]
[showif [getfile]!]
[text]line_ending=%0D%0A[/text]
[!]Generate the response[/!]
[returnraw binarybody=[getfile]]HTTP/1.0 200 OK[unurl][line_ending][/unurl][!]
[/!]Status: 200[unurl][line_ending][/unurl][!]
[/!]Content-Type: application/octet-stream[unurl][line_ending][/unurl][!]
[/!]Content-Disposition: attachment; filename="[getfile]"[unurl][line_ending][line_ending][/unurl][!]
[/!][/returnraw]
[/showif]
[!] Generate a list of download links for all files in local directory [/!]
Click on a filename to download.
[listfiles path=.]
[showif [isfile]=T]
<a href=[thisurl]?getfile=[url][filename][/url]>[filename]</a><br>
[/showif]
[/listfiles]
</BODY>
</HTML>