RFC 2068 section 10.3.6, reads: The requested resource MUST be accessed through the proxy given by the Location field. The Location field gives the URL of the proxy. The recipient is expected to repeat the request via the proxy. I tested this with M10 on both Linux 2.2.12 and Windows NT 4.0 SP3. Since the code to implement this functionality is probably just missing, I've flagged it as an all platform / all os bug.

Bulk move of all Necko (to be deleted component) bugs to new Networking component.

Moving to M17 which is now considered part of beta2.

how did 4.* behave on 305 responses? ->ruslan

Sounds like we have to fix this cuz it can be a security concern potentially. I'll see if NS4 handles this at all, I think it's 1.1-specific feature. It'll amount to implementing another redirect, which is always a pain.

Ok. I'm going to fix this. Do we have a url to test the fix?

The fix is checked in, but I'd appreaciate if somebody verifies it.

qa to me. Is there a practical example of this? I didn't know anyone used this...

benc: I have a simplistic testcase as part of my regression testing stuff, which we appear to pass. Marking VERIFIED, and stealing QA. I will be using this to do automated proxy-based tests, as well. No idea what anyone would want to do with it in real life. Transparent filtering, to redirect to a proxy which requires proxy authentication? Maybe?