Opened 14 years ago

Closed 13 years ago

#998 defect closed wontfix (wontfix)

request.setHeader should fail if data has already been sent written to the client

Reported by: mg Owned by:
Priority: high Milestone:
Component: web Keywords:
Cc: Jean-Paul Calderone, jknight, mg Branch:
Author:

Description


Change History (6)

comment:1 Changed 14 years ago by mg 

setHeader does nothing and says nothing if the response has started to be
written to the client. t.web definitely has this problem; I think t.web2
probably does too.

comment:2 Changed 14 years ago by jknight 

In web2 it would be very hard to do this by accident because of the API: 
you return a complete response. I doubt it's a good idea to change the 
behavior for t.web at this point; it'll almost certainly break something 
and has no real advantage.

comment:3 Changed 14 years ago by Jean-Paul Calderone 

Arguably, it only changes the way in which already-broken code fails, no?

comment:4 Changed 14 years ago by mg 

Yes, the code is already broken.

comment:5 Changed 13 years ago by jknight

Resolution: → wontfix
Status: new → closed

I don't think there's a good reason to change the web1 API like this.

comment:6 Changed 8 years ago by <automation>

Owner: jknight deleted
Note: See TracTickets for help on using tickets.