We are close to freezing the nsHttpChannel and the closely associated nsIHttpHeaderVistory interfaces. There are two minor issues still on the plate; otherwise this interface will be frozen for Mozilla 1.2.
The two issues are (in Darin's words) 1) are we happy with the behavior of SetRequestHeader and SetResponseHeader? Currently, these functions are additive (i.e., they append to the existing header value). Sometimes this makes sense, but often it seems contrary to the name of the function. We'll probably want to either add another param like |aReplace| to these functions or possibly add a new function named Merge/AddRequestHeader and Merge/AddResponseHeader or we could just leave it as is. 2) It would be good to move allowPipelining and redirectionLimit up into the request attributes section. This is very insignificant, but nice to have. If you have questions or comments, please send mail. Doug Turner [EMAIL PROTECTED]
