Anonymous | Login | Signup for a new account | 11-21-2024 22:35 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | |||||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
0003172 | [Quercus] | feature | always | 12-13-08 09:35 | 09-19-23 23:47 | |||||||
Reporter | koreth | View Status | public | |||||||||
Assigned To | ||||||||||||
Priority | urgent | Resolution | open | Platform | ||||||||
Status | new | OS | ||||||||||
Projection | none | OS Version | ||||||||||
ETA | none | Fixed in Version | Product Version | 4.0.0 | ||||||||
Product Build | ||||||||||||
Summary | 0003172: Add switch to ease content-length debugging | |||||||||||
Description |
If a script outputs a Content-Length header, then something somewhere spits out a bit of unexpected output, you get an error like, "tried to write 220458 bytes with content-length 217387". There should be a way to dump the entire output out to a file when that error happens, so that the output can be examined manually to figure out where the extra data is coming from. Scott and I discussed having this be a debug switch of some kind, so you don't have the overhead of saving all scripts' output all the time, just when you're trying to track this kind of problem down. |
|||||||||||
Steps To Reproduce | ||||||||||||
Additional Information | ||||||||||||
Attached Files | ||||||||||||
|
There are no notes attached to this issue. |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
33 total queries executed. 27 unique queries executed. |