creating meta bug for HTTP/1.1 compliance

Adding bugs to the meta bug

Meta bugs don't block, they depend.

updated summary to be consistent with other necko meta bugs.

Removing "[meta]" in summary in favor of keyword. Changing platform and OS to "All". Nominating for Mozilla 1.0. HTTP/1.1 compliance should be important for that release. That said, bug 15860, bug 26638, and bug 34710 don't look like they are requirements for HTTP/1.1 *compliance*, but instead cover nice-to-have enhancements that would provide additional support for HTTP/1.1. Perhaps they should be removed from the dependency list for this bug? (And possibly moved to a more appropriate meta-bug?) That leaves us with only one bug actually blocking HTTP/1.1 compliance. (Yea!) And if this meta-bug is accurate, that puts Mozilla *eerily* close to full HTTP/1.1 compliance.

we are pretty much http/1.1 compliant, but there are many features of http/1.1 that we don't exploit. there are also several http/1.1 compliance bugs that are not included on this meta bug. in particular, we don't properly handle some http/1.1 cache control headers. the [meta] summary prefix is how necko meta bugs are tagged. adding a meta keyword is fine if that helps you, but please do not remove the [meta] prefix since people currently use that in their bugzilla queries.

batch: adding topembed per Gecko2 document http://rocknroll.mcom.com/users/marek/publish/Gecko/Gecko2Tasks.html

Bulk adding topembed keyword. Gecko/embedding needed.

Should this bug depend on bug 49172, or should another [meta] bug be created for "full HTTP/1.1 support" (as opposed to minimum compliance, since this appears to be a "should"), much like bug 7954 collects "outstanding issues for full HTML 4.01 support"? Would such a collection, if created, contain any other bugs?

Added bug 198309, 205 Reset Content, as a dependancy.

Added bug 8648 and bug 205228, both for 301 Moved Permanently, as dependancies.

Removed dependencies on bug 8648, bug 198309, bug 205228. Brian, this meta bug is for tracking HTTP/1.1 *compliance*; not just anything intelligent the browser could do with HTTP response codes. So to answer your question, yes, please do create another meta bug if you think other HTTP support issues warrant tracking that way.

-> default owner

this is down to one bug - we don't need a meta tracker