W3C home > Mailing lists > Public > public-webapi@w3.org > October 2006

Re: ISSUE-98: open(): requesting a URI with a fragment identifier

From: Joao Eiras <joao.eiras@gmail.com>
Date: Sun, 29 Oct 2006 14:53:44 -0000
To: "Web APIs WG" <public-webapi@w3.org>
Message-ID: <op.th6ubuzkxl3at9@dragast>

What happens if there's a base element pointing to http://www.example.com/  
Note: rfc 1808 clearly states that fragment identifier are ALWAYS resolved  
within the same document, and therefore base/@href must be disregarded.

For me, Gecko's behaviour could be considered a bug.. no ?

Anyway, requesting a url with a fragment identifier, should be the same as  
requesting the current document.

  Web APIs Issue Tracker <dean+cgi@w3.org> escreveu:

> ISSUE-98: open(): requesting a URI with a fragment identifier
> http://www.w3.org/2005/06/tracker/webapi/issues/98
> Raised by: Anne van Kesteren
> On product: XMLHttpRequest
> http://tc.labs.opera.com/apis/XMLHttpRequest/open/017.htm suggests that
> Internet Explorer and Opera literrally request "017.txt#foobar" from the
> server, where Firefox just requests "017.txt".
> Anyone with good arguments for keeping either behavior?
Received on Sunday, 29 October 2006 14:53:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:22 UTC