Actions
Bug #1383
closedWt::Http::Message header client-length causing bad request
Start date:
08/01/2012
Due date:
% Done:
0%
Estimated time:
Description
When the setHeader method is used to set the Client-Length header it adds a second Client-Length header. It causes a 400 response : Bad Request.
Absolutely not blocking since it is in fact filled automatically, but i lost some time finding that out.
Possible to test with the attached file.
Files
Updated by Koen Deforche about 12 years ago
- Assignee set to Koen Deforche
- Target version set to 3.2.3
Updated by Koen Deforche about 12 years ago
- Status changed from New to InProgress
Updated by Koen Deforche about 12 years ago
- Target version changed from 3.2.3 to 3.3.0
Updated by Koen Deforche almost 12 years ago
- Status changed from InProgress to Resolved
Updated by Koen Deforche almost 12 years ago
- Status changed from Resolved to Closed
Actions