1 <?xml version="1.0" encoding="ISO-8859-1"?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!--
4 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
5 This file is generated from xml source: DO NOT EDIT
6 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
8 <title>mod_headers - Apache HTTP Server</title>
9 <link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
10 <link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
11 <link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
12 <script src="../style/scripts/prettify.js" type="text/javascript">
15 <link href="../images/favicon.ico" rel="shortcut icon" /></head>
17 <div id="page-header">
18 <p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p>
19 <p class="apache">Apache HTTP Server Version 2.5</p>
20 <img alt="" src="../images/feather.gif" /></div>
21 <div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div>
23 <a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.5</a> > <a href="./">Modules</a></div>
24 <div id="page-content">
25 <div id="preamble"><h1>Apache Module mod_headers</h1>
27 <p><span>Available Languages: </span><a href="../en/mod/mod_headers.html" title="English"> en </a> |
28 <a href="../fr/mod/mod_headers.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
29 <a href="../ja/mod/mod_headers.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
30 <a href="../ko/mod/mod_headers.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
32 <table class="module"><tr><th><a href="module-dict.html#Description">Description:</a></th><td>Customization of HTTP request and response
34 <tr><th><a href="module-dict.html#Status">Status:</a></th><td>Extension</td></tr>
35 <tr><th><a href="module-dict.html#ModuleIdentifier">Module Identifier:</a></th><td>headers_module</td></tr>
36 <tr><th><a href="module-dict.html#SourceFile">Source File:</a></th><td>mod_headers.c</td></tr></table>
39 <p>This module provides directives to control and modify HTTP
40 request and response headers. Headers can be merged, replaced
43 <div id="quickview"><h3 class="directives">Directives</h3>
45 <li><img alt="" src="../images/down.gif" /> <a href="#header">Header</a></li>
46 <li><img alt="" src="../images/down.gif" /> <a href="#requestheader">RequestHeader</a></li>
50 <li><img alt="" src="../images/down.gif" /> <a href="#order">Order of Processing</a></li>
51 <li><img alt="" src="../images/down.gif" /> <a href="#early">Early and Late Processing</a></li>
52 <li><img alt="" src="../images/down.gif" /> <a href="#examples">Examples</a></li>
53 </ul><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div>
54 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
56 <h2><a name="order" id="order">Order of Processing</a></h2>
58 <p>The directives provided by <code class="module"><a href="../mod/mod_headers.html">mod_headers</a></code> can
59 occur almost anywhere within the server configuration, and can be
60 limited in scope by enclosing them in <a href="../sections.html">configuration sections</a>.</p>
62 <p>Order of processing is important and is affected both by the
63 order in the configuration file and by placement in <a href="../sections.html#mergin">configuration sections</a>. These
64 two directives have a different effect if reversed:</p>
66 <pre class="prettyprint lang-config">
67 RequestHeader append MirrorID "mirror 12"
68 RequestHeader unset MirrorID
72 <p>This way round, the <code>MirrorID</code> header is not set. If
73 reversed, the MirrorID header is set to "mirror 12".</p>
74 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
76 <h2><a name="early" id="early">Early and Late Processing</a></h2>
77 <p><code class="module"><a href="../mod/mod_headers.html">mod_headers</a></code> can be applied either early or late
78 in the request. The normal mode is late, when <em>Request</em> Headers are
79 set immediately before running the content generator and <em>Response</em>
80 Headers just as the response is sent down the wire. Always use
81 Late mode in an operational server.</p>
83 <p>Early mode is designed as a test/debugging aid for developers.
84 Directives defined using the <code>early</code> keyword are set
85 right at the beginning of processing the request. This means
86 they can be used to simulate different requests and set up test
87 cases, but it also means that headers may be changed at any time
88 by other modules before generating a Response.</p>
90 <p>Because early directives are processed before the request path's
91 configuration is traversed, early headers can only be set in a
92 main server or virtual host context. Early directives cannot depend
93 on a request path, so they will fail in contexts such as
94 <code><Directory></code> or <code><Location></code>.</p>
95 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
97 <h2><a name="examples" id="examples">Examples</a></h2>
101 Copy all request headers that begin with "TS" to the
104 <pre class="prettyprint lang-config">
111 Add a header, <code>MyHeader</code>, to the response including a
112 timestamp for when the request was received and how long it
113 took to begin serving the request. This header can be used by
114 the client to intuit load on the server or in isolating
115 bottlenecks between the client and the server.
117 <pre class="prettyprint lang-config">
118 Header set MyHeader "%D %t"
122 <p>results in this header being added to the response:</p>
124 <div class="example"><p><code>
125 MyHeader: D=3775428 t=991424704447256
132 <pre class="prettyprint lang-config">
133 Header set MyHeader "Hello Joe. It took %D microseconds for Apache to serve this request."
137 <p>results in this header being added to the response:</p>
139 <div class="example"><p><code>
140 MyHeader: Hello Joe. It took D=3775428 microseconds for Apache
141 to serve this request.
146 Conditionally send <code>MyHeader</code> on the response if and
147 only if header <code>MyRequestHeader</code> is present on the request.
148 This is useful for constructing headers in response to some client
149 stimulus. Note that this example requires the services of the
150 <code class="module"><a href="../mod/mod_setenvif.html">mod_setenvif</a></code> module.
152 <pre class="prettyprint lang-config">
153 SetEnvIf MyRequestHeader myvalue HAVE_MyRequestHeader
154 Header set MyHeader "%D %t mytext" env=HAVE_MyRequestHeader
158 <p>If the header <code>MyRequestHeader: myvalue</code> is present on
159 the HTTP request, the response will contain the following header:</p>
161 <div class="example"><p><code>
162 MyHeader: D=3775428 t=991424704447256 mytext
167 Enable DAV to work with Apache running HTTP through SSL hardware
168 (<a href="http://svn.haxx.se/users/archive-2006-03/0549.shtml">problem
169 description</a>) by replacing <var>https:</var> with
170 <var>http:</var> in the <var>Destination</var> header:
172 <pre class="prettyprint lang-config">
173 RequestHeader edit Destination ^https: http: early
179 Set the same header value under multiple non-exclusive conditions,
180 but do not duplicate the value in the final header.
181 If all of the following conditions applied to a request (i.e.,
182 if the <code>CGI</code>, <code>NO_CACHE</code> and
183 <code>NO_STORE</code> environment variables all existed for the
186 <pre class="prettyprint lang-config">
187 Header merge Cache-Control no-cache env=CGI
188 Header merge Cache-Control no-cache env=NO_CACHE
189 Header merge Cache-Control no-store env=NO_STORE
193 <p>then the response would contain the following header:</p>
195 <div class="example"><p><code>
196 Cache-Control: no-cache, no-store
199 <p>If <code>append</code> was used instead of <code>merge</code>,
200 then the response would contain the following header:</p>
202 <div class="example"><p><code>
203 Cache-Control: no-cache, no-cache, no-store
207 Set a test cookie if and only if the client didn't send us a cookie
208 <pre class="prettyprint lang-config">
209 Header set Set-Cookie testcookie "expr=-z %{req:Cookie}"
215 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
216 <div class="directive-section"><h2><a name="Header" id="Header">Header</a> <a name="header" id="header">Directive</a></h2>
217 <table class="directive">
218 <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Configure HTTP response headers</td></tr>
219 <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>Header [<var>condition</var>] add|append|echo|edit|merge|set|unset
220 <var>header</var> [<var>value</var>] [early|env=[!]<var>variable</var>]</code></td></tr>
221 <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
222 <tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
223 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
224 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_headers</td></tr>
225 <tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Default condition was temporarily changed to "always" in 2.3.9 and 2.3.10</td></tr>
227 <p>This directive can replace, merge or remove HTTP response
228 headers. The header is modified just after the content handler
229 and output filters are run, allowing outgoing headers to be
232 <p> The optional <var>condition</var> argument determines which internal
233 table of responses headers this directive will operate against. Other
234 components of the server may have stored their response headers in either
235 the table that corresponds to <code>onsuccess</code> or the table that
236 corresponds to <code>always</code>. "Always" in this context refers to
237 whether headers you add will be sent during both a successful and unsucessful
238 response, but if your action is a function of an existing header, you
239 will have to read on for further complications.</p>
241 <p> The default value of <code>onsuccess</code> may need to be changed to
242 <code>always</code> under the circumstances similar to those listed below.
243 Note also that repeating this directive with both conditions makes sense in
244 some scenarios because <code>always</code> is not a superset of
245 <code>onsuccess</code> with respect to existing headers:</p>
248 <li> You're adding a header to a non-success (non-2xx) response, such
249 as a redirect, in which case only the table corresponding to
250 <code>always</code> is used in the ultimate response.</li>
251 <li> You're modifying or removing a header generated by a CGI script,
252 in which case the CGI scripts are in the table corresponding to
253 <code>always</code> and not in the default table.</li>
254 <li> You're modifying or removing a header generated by some piece of
255 the server but that header is not being found by the default
256 <code>onsuccess</code> condition.</li>
259 <p>The action it performs is determined by the first
260 argument (second argument if a <var>condition</var> is specified).
261 This can be one of the following values:</p>
264 <dt><code>add</code></dt>
265 <dd>The response header is added to the existing set of headers,
266 even if this header already exists. This can result in two
267 (or more) headers having the same name. This can lead to
268 unforeseen consequences, and in general <code>set</code>,
269 <code>append</code> or <code>merge</code> should be used instead.</dd>
271 <dt><code>append</code></dt>
272 <dd>The response header is appended to any existing header of
273 the same name. When a new value is merged onto an existing
274 header it is separated from the existing header with a comma.
275 This is the HTTP standard way of giving a header multiple values.</dd>
277 <dt><code>echo</code></dt>
278 <dd>Request headers with this name are echoed back in the
279 response headers. <var>header</var> may be a
280 <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular expression</a>.
281 <var>value</var> must be omitted.</dd>
283 <dt><code>edit</code></dt>
284 <dd>If this response header exists, its value is transformed according
285 to a <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular expression</a>
286 search-and-replace. The <var>value</var> argument is a <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular expression</a>, and the <var>replacement</var>
287 is a replacement string, which may contain backreferences.</dd>
289 <dt><code>merge</code></dt>
290 <dd>The response header is appended to any existing header of
291 the same name, unless the value to be appended already appears in the
292 header's comma-delimited list of values. When a new value is merged onto
293 an existing header it is separated from the existing header with a comma.
294 This is the HTTP standard way of giving a header multiple values.
295 Values are compared in a case sensitive manner, and after
296 all format specifiers have been processed. Values in double quotes
297 are considered different from otherwise identical unquoted values.</dd>
299 <dt><code>set</code></dt>
300 <dd>The response header is set, replacing any previous header
301 with this name. The <var>value</var> may be a format string.</dd>
303 <dt><code>unset</code></dt>
304 <dd>The response header of this name is removed, if it exists.
305 If there are multiple headers of the same name, all will be
306 removed. <var>value</var> must be omitted.</dd>
309 <p>This argument is followed by a <var>header</var> name, which
310 can include the final colon, but it is not required. Case is
311 ignored for <code>set</code>, <code>append</code>, <code>merge</code>,
312 <code>add</code>, <code>unset</code> and <code>edit</code>.
313 The <var>header</var> name for <code>echo</code>
314 is case sensitive and may be a <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular
317 <p>For <code>set</code>, <code>append</code>, <code>merge</code> and
318 <code>add</code> a <var>value</var> is specified as the next argument.
320 contains spaces, it should be surrounded by double quotes.
321 <var>value</var> may be a character string, a string containing format
322 specifiers or a combination of both. The following format specifiers
323 are supported in <var>value</var>:</p>
325 <table class="bordered"><tr class="header"><th>Format</th><th>Description</th></tr>
326 <tr><td><code>%%</code></td>
327 <td>The percent sign</td></tr>
328 <tr class="odd"><td><code>%t</code></td>
329 <td>The time the request was received in Universal Coordinated Time
330 since the epoch (Jan. 1, 1970) measured in microseconds. The value
331 is preceded by <code>t=</code>.</td></tr>
332 <tr><td><code>%D</code></td>
333 <td>The time from when the request was received to the time the
334 headers are sent on the wire. This is a measure of the duration
335 of the request. The value is preceded by <code>D=</code>.
336 The value is measured in microseconds.</td></tr>
337 <tr class="odd"><td><code>%{VARNAME}e</code></td>
338 <td>The contents of the <a href="../env.html">environment
339 variable</a> <code>VARNAME</code>.</td></tr>
340 <tr><td><code>%{VARNAME}s</code></td>
341 <td>The contents of the <a href="mod_ssl.html#envvars">SSL environment
342 variable</a> <code>VARNAME</code>, if <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> is enabled.</td></tr>
345 <div class="note"><h3>Note</h3>
346 <p>The <code>%s</code> format specifier is only available in
347 Apache 2.1 and later; it can be used instead of <code>%e</code>
348 to avoid the overhead of enabling <code>SSLOptions
349 +StdEnvVars</code>. If <code>SSLOptions +StdEnvVars</code> must
350 be enabled anyway for some other reason, <code>%e</code> will be
351 more efficient than <code>%s</code>.</p>
354 <p>For <code>edit</code> there is both a <var>value</var> argument
355 which is a <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular expression</a>,
356 and an additional <var>replacement</var> string.</p>
358 <p>The <code class="directive">Header</code> directive may be followed by
359 an additional argument, which may be any of:</p>
361 <dt><code>early</code></dt>
362 <dd>Specifies <a href="#early">early processing</a>.</dd>
363 <dt><code>env=[!]<var>varname</var></code></dt>
364 <dd>The directive is applied if and only if the <a href="../env.html">environment variable</a> <code>varname</code> exists.
365 A <code>!</code> in front of <code>varname</code> reverses the test,
366 so the directive applies only if <code>varname</code> is unset.</dd>
367 <dt><code>expr=<var>expression</var></code></dt>
368 <dd>The directive is applied if and only if <var>expression</var>
369 evaluates to true. Details of expression syntax and evaluation are
370 documented in the <a href="../expr.html">ap_expr</a> documentation.</dd>
373 <p>Except in <a href="#early">early</a> mode, the
374 <code class="directive">Header</code> directives are processed just
375 before the response is sent to the network. These means that it is
376 possible to set and/or override most headers, except for those headers
377 added by the HTTP header filter, such as Content-Type.</p>
380 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
381 <div class="directive-section"><h2><a name="RequestHeader" id="RequestHeader">RequestHeader</a> <a name="requestheader" id="requestheader">Directive</a></h2>
382 <table class="directive">
383 <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Configure HTTP request headers</td></tr>
384 <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>RequestHeader add|append|edit|edit*|merge|set|unset <var>header</var>
385 [<var>value</var>] [<var>replacement</var>] [early|env=[!]<var>variable</var>]</code></td></tr>
386 <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
387 <tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
388 <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
389 <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_headers</td></tr>
391 <p>This directive can replace, merge, change or remove HTTP request
392 headers. The header is modified just before the content handler
393 is run, allowing incoming headers to be modified. The action it
394 performs is determined by the first argument. This can be one
395 of the following values:</p>
399 <dt><code>add</code></dt>
400 <dd>The request header is added to the existing set of headers,
401 even if this header already exists. This can result in two
402 (or more) headers having the same name. This can lead to
403 unforeseen consequences, and in general <code>set</code>,
404 <code>append</code> or <code>merge</code> should be used instead.</dd>
406 <dt><code>append</code></dt>
407 <dd>The request header is appended to any existing header of the
408 same name. When a new value is merged onto an existing header
409 it is separated from the existing header with a comma. This
410 is the HTTP standard way of giving a header multiple
413 <dt><code>edit</code></dt>
414 <dt><code>edit*</code></dt>
415 <dd>If this request header exists, its value is transformed according
416 to a <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular expression</a>
417 search-and-replace. The <var>value</var> argument is a <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular expression</a>, and the <var>replacement</var>
418 is a replacement string, which may contain backreferences.
419 The <code>edit</code> form will match and replace exactly once
420 in a header value, whereas the <code>edit*</code> form will replace
421 <em>every</em> instance of the search pattern if it appears more
424 <dt><code>merge</code></dt>
425 <dd>The request header is appended to any existing header of
426 the same name, unless the value to be appended already appears in the
427 existing header's comma-delimited list of values. When a new value is
428 merged onto an existing header it is separated from the existing header
429 with a comma. This is the HTTP standard way of giving a header multiple
430 values. Values are compared in a case sensitive manner, and after
431 all format specifiers have been processed. Values in double quotes
432 are considered different from otherwise identical unquoted values.</dd>
434 <dt><code>set</code></dt>
435 <dd>The request header is set, replacing any previous header
438 <dt><code>unset</code></dt>
439 <dd>The request header of this name is removed, if it exists. If
440 there are multiple headers of the same name, all will be removed.
441 <var>value</var> must be omitted.</dd>
444 <p>This argument is followed by a header name, which can
445 include the final colon, but it is not required. Case is
446 ignored. For <code>set</code>, <code>append</code>, <code>merge</code> and
447 <code>add</code> a <var>value</var> is given as the third argument. If a
448 <var>value</var> contains spaces, it should be surrounded by double
449 quotes. For <code>unset</code>, no <var>value</var> should be given.
450 <var>value</var> may be a character string, a string containing format
451 specifiers or a combination of both. The supported format specifiers
452 are the same as for the <code class="directive"><a href="#header">Header</a></code>,
453 please have a look there for details. For <code>edit</code> both
454 a <var>value</var> and a <var>replacement</var> are required, and are
455 a <a class="glossarylink" href="../glossary.html#regex" title="see glossary">regular expression</a> and a
456 replacement string respectively.</p>
458 <p>The <code class="directive">RequestHeader</code> directive may be followed by
459 an additional argument, which may be any of:</p>
461 <dt><code>early</code></dt>
462 <dd>Specifies <a href="#early">early processing</a>.</dd>
463 <dt><code>env=[!]<var>varname</var></code></dt>
464 <dd>The directive is applied if and only if the <a href="../env.html">environment variable</a> <code>varname</code> exists.
465 A <code>!</code> in front of <code>varname</code> reverses the test,
466 so the directive applies only if <code>varname</code> is unset.</dd>
467 <dt><code>expr=<var>expression</var></code></dt>
468 <dd>The directive is applied if and only if <var>expression</var>
469 evaluates to true. Details of expression syntax and evaluation are
470 documented in the <a href="../expr.html">ap_expr</a> documentation.</dd>
473 <p>Except in <a href="#early">early</a> mode, the
474 <code class="directive">RequestHeader</code> directive is processed
475 just before the request is run by its handler in the fixup phase.
476 This should allow headers generated by the browser, or by Apache
477 input filters to be overridden or modified.</p>
481 <div class="bottomlang">
482 <p><span>Available Languages: </span><a href="../en/mod/mod_headers.html" title="English"> en </a> |
483 <a href="../fr/mod/mod_headers.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
484 <a href="../ja/mod/mod_headers.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
485 <a href="../ko/mod/mod_headers.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
486 </div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>This section is experimental!</strong><br />Comments placed here should not be expected
487 to last beyond the testing phase of this system, nor do we in any way guarantee that we'll read them.</div>
488 <div id="disqus_thread">
489 </div><script type="text/javascript"><!--//--><![CDATA[//><!--
491 var disqus_shortname = 'httpd';
492 var disqus_identifier = window.location.href.replace(/(current|trunk)/, "2.4").replace(/\/[a-z]{2}\//, "/").replace(window.location.protocol, "http:") + '.' + lang;
493 if (disqus_identifier.indexOf("httpd.apache.org") != -1) {
495 var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
496 dsq.src = window.location.protocol + '//' + disqus_shortname + '.disqus.com/embed.js';
497 (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
500 var text = document.createTextNode("Comments have been disabled for offline viewing.");
501 document.getElementById('disqus_thread').appendChild(text);
503 //--><!]]></script></div><div id="footer">
504 <p class="apache">Copyright 2012 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
505 <p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
506 if (typeof(prettyPrint) !== undefined) {