[whatwg] Access the Response Headers for the Current Document

[Michael Enright]

Is it possible that the usage of HTTP to obtain a document for rendering and
to obtain a document for XHR would differ sufficiently that the HTTP headers
would differ?

On Wed, Jul 15, 2009 at 12:07 PM, Joseph Pecoraro <joepeck02 at gmail.com>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.
>
> 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)
>
> Cheers,
> Joseph Pecoraro
>
> [1] Example: http://bogojoker.com/x/xhr/headers.html
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090715/8bda92a3/attachment.htm>