W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2009

[whatwg] Access the Response Headers for the Current Document

From: Ian Hickson <ian@hixie.ch>
Date: Wed, 29 Jul 2009 01:21:27 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0907290120020.3189@hixie.dreamhostps.com>
On Wed, 15 Jul 2009, Joseph Pecoraro wrote:
>
> It seems like an oversight that Javascript can read response headers off 
> of XHR but not for the current document.  So in order to find out the 
> headers for the current document you would need to make another request, 
> refetching the current page, to find that out [1].
> 
> Use Cases:
> Any that apply to XHR accessing their response headers would certainly 
> apply here.  Some thoughts are accessing the Content-Type header or 
> Custom Headers and acting accordingly.

You can just include the data straight into the page, for now. It's really 
clear what the use cases would actually be in practice.


> Come up with a clear description of the problem that needs to be solved: 
> Cannot access the Response Headers for the current document in 
> Javascript.
> 
> Any there Browser Implementors out there that agree with this?  If so, 
> any thoughts on the best ways to expose the current page's request 
> headers to Javascript?  Certainly they are readonly, modifying them 
> seems to be useless. How about keeping consistent with the XHR interface 
> with something like:
> 
>   document.getAllResponseHeaders() and document.getResponseHeader(header)

This is something that might make sense for a future version, but in the 
absence of a compelling need for this, I'm going to skip adding this in 
this version.

Cheers,
-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 28 July 2009 18:21:27 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:14 UTC