Frank McCown wrote:
According to rfc1808 sec 5.2, the ".." should be left at the beginning
of the URL path. But according to the new rfc3986 sec 5.4.2, the ".."
should be removed from the beginning of the URL path.
With this new behavior implemented, wget would never make a URL
request with
According to rfc1808 sec 5.2, the ".." should be left at the beginning
of the URL path. But according to the new rfc3986 sec 5.4.2, the ".."
should be removed from the beginning of the URL path.
With this new behavior implemented, wget would never make a URL request
with ".." in it except in
Hrvoje Niksic wrote:
Frank McCown <[EMAIL PROTECTED]> writes:
Earlier today I sent an email explaining that wget already handles
".." in the middle of a URL correctly, it just doesn't handle ".."
immediately after the domain name correctly.
But it does, at least according to rfc1808, which
Frank McCown <[EMAIL PROTECTED]> writes:
> Earlier today I sent an email explaining that wget already handles
> ".." in the middle of a URL correctly, it just doesn't handle ".."
> immediately after the domain name correctly.
But it does, at least according to rfc1808, which mandates leading
".."
Hrvoje Niksic wrote:
Frank McCown <[EMAIL PROTECTED]> writes:
But IIS does not handle ".." the same way. IIS will simply ignore
".." and produce the page. So the following two URLs are referencing
the same HTML page:
http://www.merseyfire.gov.uk/pages/fire_auth/councillors.htm
and
http://
Frank McCown <[EMAIL PROTECTED]> writes:
> But IIS does not handle ".." the same way. IIS will simply ignore
> ".." and produce the page. So the following two URLs are referencing
> the same HTML page:
>
> http://www.merseyfire.gov.uk/pages/fire_auth/councillors.htm
>
> and
>
> http://www.mersey
Mauro Tortonesi wrote:
Frank McCown wrote:
It would be nice if wget could handle these mal-adjusted URLs properly
since they do appear from time to time. (In the case of
www.merseyfire.gov.uk, they appear very frequently unfortunately.)
yes, it would be nice. but how are you exactly propos
Frank McCown wrote:
It would be nice if wget could handle these mal-adjusted URLs properly
since they do appear from time to time. (In the case of
www.merseyfire.gov.uk, they appear very frequently unfortunately.)
yes, it would be nice. but how are you exactly proposing to achieve this
resu
Apache does not allow a URL to attempt access above the public_html
location. Example:
http://www.gnu.org/../software/wget/manual/wget.html
will cause a "Bad Request" page to be generated because the ".." in the
URL.
But IIS does not handle ".." the same way. IIS will simply ignore ".."
a
