* Myk Melez <[EMAIL PROTECTED]> [2007-01-04 15:30-0800]
> Boris Zbarsky wrote:
> >Preethi Natarajan wrote:
> >>While going through all.js, I found another interesting parameter
> >>value specification:
> >>
> >> pref("network.http.pipelining" , false);
> >>
> >> Does this mean that the HTTP requests will not be pipelined?
> >
> >Yes. Enabling that causes issues with various sites due to broken
> >servers and possibly due to bugs in the pipelining code in necko.
>
> Is there any way to sniff the broken servers and selectively disable
> pipelining for them, or are we consigned to never enabling this feature
> (nor fixing the bugs in our code)?I'd be interested in examining one such server to see how it fails and how one might detect and deal. > -myk > _______________________________________________ > dev-tech-network mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-tech-network -- -eric office: +1.617.258.5741 NE43-344, MIT, Cambridge, MA 02144 USA cell: +1.857.222.5741 ([EMAIL PROTECTED]) Feel free to forward this message to any list for any purpose other than email address distribution.
signature.asc
Description: Digital signature
_______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
