W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2011

Re: Remaining issues related to redirects [#43 #295]

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sat, 03 Sep 2011 14:26:58 +0200
Message-ID: <4E621D12.2080306@gmx.de>
To: Mark Nottingham <mnot@mnot.net>
CC: HTTP Working Group <ietf-http-wg@w3.org>
On 2011-09-02 12:47, Julian Reschke wrote:
> On 2011-09-02 03:06, Mark Nottingham wrote:
>> ...
>> Having HTTP define fragment combination (both in the single and dual
>> cases) makes sense, because IME, client-side stacks handle HTTP
>> redirects automatically, before the format-specific machinery ever
>> gets to see the HTTP. Requiring -- or even allowing -- that this be
>> format-specific opens up a huge can of worms in most implementations,
>> and makes the Web a much more complex place.
>> ...
>
> I agree that having it format-specific makes the web more complex; but
> right now this is the case; for instance, fragment recombination works
> different for HTML and PDF, as far as I can tell.
> ...

...expanding on this -- tested with FF and Reader plugin; accessing 
a.pdf#foo, getting redirected to b.pdf#bar yields b.pdf#foo in the 
address bar (I don't believe it's the plugin's fault).

Best regards, Julian
Received on Saturday, 3 September 2011 12:27:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:47 GMT