[Webkit-unassigned] [Bug 26994] Store non-standard HTTP headers in history

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Sep 24 06:57:03 PDT 2009


https://bugs.webkit.org/show_bug.cgi?id=26994





--- Comment #9 from Marshall Greenblatt <magreenblatt at gmail.com>  2009-09-24 06:57:03 PDT ---
(In reply to comment #8)
> (From update of attachment 40031 [details])
> Why would different clients want to store different headers in the history
> item?  It seems like we should store all the headers except some specific list
> of headers that are problematic.  (Which are the problematic headers?)

Headers in any of the following categories should not be stored in the history.

1. Transfer and/or content negotiation.

Accept-Ranges, Content-Encoding, Content-Length, Content-Location, Content-MD5,
Content-Range, Content-Type, If-Range, Range, TE, Trailer, Transfer-Encoding,
Via

2. Managed state information.

Authorization, Cookie, Host, Proxy-Authorization, Referer.

3. Browser capabilities.

Accept, Accept-Charset, Accept-Encoding, Accept-Language, Expect, Upgrade,
User-Agent.


Am I missing any?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list