[EMAIL PROTECTED] wrote:
According to RFC 2396[1] section 5.2:
RFC 2396 is obsolete. It was superseded by RFC 3986 / STD 66 early this year.
In particular, the procedure for removing dot-segments from the path component
of a URI reference -- a procedure that is only supposed to be done when
On Thu, Sep 08, 2005 at 12:41:39PM -0600, Mike Brown wrote:
[EMAIL PROTECTED] wrote:
According to RFC 2396[1] section 5.2:
RFC 2396 is obsolete. It was superseded by RFC 3986 / STD 66 early this year.
Thanks for the correction.
Jeff
pgpFDXgf6EeqZ.pgp
Description: PGP signature
[EMAIL PROTECTED] wrote in news:[EMAIL PROTECTED]:
According to RFC 2396[1] section 5.2:
g) If the resulting buffer string still begins with one or more
complete path segments of .., then the reference is
considered to be in error. Implementations may handle this
Hi Duncan,
On Tue, Sep 06, 2005 at 12:51:24PM +0100, Duncan Booth wrote:
The net effect of this is that on some sites using a Python spider (e.g.
webchecker.py) will produce a large number of error messages for links
which browsers will actually resolve successfully.
As far as I'm
Hello,
I'm using the module urlparse and I think I've found a bug in the
urlparse module. When you merge an url and a link
like../../../page.html with urljoin, the new url created keep some
../ in it. Here is an example :
import urlparse
begin = http://www.example.com/folder/page.html;
On 9/4/05, Fabien Schwob [EMAIL PROTECTED] wrote:
Hello,
I'm using the module urlparse and I think I've found a bug in the
urlparse module. When you merge an url and a link
like../../../page.html with urljoin, the new url created keep some
../ in it. Here is an example :
import
import urlparse
begin = http://www.example.com/folder/page.html;
end = ../../../otherpage.html
urlparse.urljoin(begin, end)
'http://www.example.com/../../otherpage.html'
You seem to be typing this from memory; the example actually gives a
single set of ../, not two.
No, it's a copy of
According to RFC 2396[1] section 5.2:
g) If the resulting buffer string still begins with one or more
complete path segments of .., then the reference is
considered to be in error. Implementations may handle this
error by retaining these components in the
