Our Accept: header is currently "*/*".
Over in http://bugzilla.mozilla.org/show_bug.cgi?id=58040 I have a patch
to make it a pref. However, just after I made it (congrats to whoever
wrote that code, by the way - it was really obvious what to do)
http-rearch landed and probably broke it (although I haven't checked.)
Before I recreate the patch, I thought I would check in here. You see, I
have been told that there are arguments _against_ making it a pref rather
than hardcoded */*. I just wanted to see if anyone will object when I do
this again.
The advantages of it being a pref. are numerous:
- We can have a nice big argument about what it should be (the current
candidate is
Accept: text/xml;q=1, text/html;q=0.9, image/png;q=1, image/jpeg;q=1,
image/gif;q=0.9, text/plain;q=0.8, text/css;q=1, */*;q=0.01 ) and then
change it easily when we decide. This is a world away from the "4k Accept
header" problem in early Netscape versions.
- Embedders can change it to match the capabilities of their particular
Mozilla subset
- Mozilla extension providers (using XPIs) can use signed scripts to add
e.g. application/svg+xml or whatever to the Accept: header.
Does anyone object to this course of action? It goes without saying that
this pref would have _no_ user UI.
Gerv
