Confirmed users
431
edits
Necko: Electrolysis design and subprojects: Difference between revisions
Jump to navigation
Jump to search
Necko: Electrolysis design and subprojects (view source)
Revision as of 01:07, 2 September 2009
, 2 September 2009→HTTP Headers
| Line 35: | Line 35: | ||
==== HTTP Headers ==== | ==== HTTP Headers ==== | ||
HTTP headers will need to be parsed first in the chrome process--so things like auth, cache directives, cookies, etc., can be handled. We will also need to provide some or all headers to the content process, probably via serializing them over IPDL. | HTTP headers will need to be parsed first in the chrome process--so things like auth, cache directives, cookies, etc., can be handled. We will also need to provide some or all headers to the content process, probably via serializing them over IPDL. | ||
* bz suggests we "whitelist" the headers and provide only needed headers to the content process. | * bz suggests we "whitelist" the headers and provide only needed headers to the content process. | ||
* we may need to ship the request headers as well as the reply headers to the content process, in order for nsIHttpChannel::getRequestHeader() to work | |||
** Will content process need, or are all uses in chrome? Currently only called by | |||
*** nsDocument to get Http Referer (this is probably in content?) | |||
*** nsXMLRequest to get Content-Type (to see if preflight request needed) | |||
*** nsFeedSniffer to see if X-Moz-Is-Feed is set | |||
*** nsIncrementalDownload to keep range header when redirect occurs (chrome?) | |||
*** nsViewsourceChannel to forward getRequestHeader to underlying nsHttpChannel | |||
==== HTTP redirects ==== | ==== HTTP redirects ==== | ||