[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev Can't access a site: Alert!: HTTP/1.1 400 Bad Request

From: David Woolley
Subject: Re: lynx-dev Can't access a site: Alert!: HTTP/1.1 400 Bad Request
Date: Wed, 12 Feb 2003 21:03:21 +0000 (GMT)


Misconfigured server.  They respond with the following:

  HTTP/1.0 302 Found
  Date: Wed, 12 Feb 2003 20:54:31 GMT
  Content-Type: text/html
  Server: Apache/1.3.27 (Unix) mod_perl/1.26 mod_jk2/2.0.0 mod_log_bytes/0.3 
  bwlimited/1.0 PHP/4.3.0 FrontPage/ mod_ssl/2.8.12 OpenSSL/0.9.6b
  X-Powered-By: PHP/4.3.0
  Location: ../loja/default.php
  Via: 1.1 anchor-cache-01 (NetCache NetApp/5.3.1R2)

This is a temporary redirect, attempting to reference a home page.  Firstly
it is a violation of the protocol to send a relative URL at this point.
Secondly, the only reasonable way of interpreting it is relative to the URL
that was originally requested, but that URL refers to the server root, and
you can't go above the server root using ..

A browser is expected to strip back components from the base URL when it gets
a leading ..s in relative URLs.  If this takes it back to the root, it is 
an error.  One policy, which seems to be the one used by Lynx, is to send
the .. through and hope it means something.

You are, though, dealing with a double fault, and it is anyone's guess as to
what is really meant, although it sounds like stripping the bogus .. produces
the right result in this case..

(Note relative URLs can be used in CGI generated redirects, but only within
the server.  The server should service such redirects locally and return the
redirected page in the initial response (albeit with a header giving the
corrected location)).

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]