Summary: | Would like to see http request & response headers | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | Jim Mahood <kde> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | CONFIRMED --- | ||
Severity: | wishlist | CC: | kdelibs-bugs |
Priority: | NOR | ||
Version: | 5.48.0 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Jim Mahood
2004-12-10 15:50:44 UTC
The response headers are already visible. CTRL+I or View->Document Information. Request headers are not likely to be implemented. I don't think they're particularly necessary anyway, do you? If you compile with debug info enabled http will be able to log both request and response headers to file. See the last section in kdebase/kioslave/DEBUG.howto It might be useful to make that possible with non-debug builds as well indeed. The Document Information dialog is good, but I can't select any values in there, so it's not that useful to me. Request headers are useful for debugging authorization and/or cookie problems. Or, for instance, if I'm on a site that maintains state with cookies and want to fetch something with a different client, or from a different host (with wget, for instance), that requires that cookie value, a quick look at the request headers gives me what I need. Otherwise, I have to go through the cookie configuration, find the host, and reconstruct the Cookie header myself, since Name/value pairs are broken out into separate fields in there. So adding a copy action would be sufficient? Making that text copyable would be helpful in general, but not sufficient for what I'm requesting. I like the debug logging that Waldo pointed out, and I agree that it would be helpful to make this available with non-debug builds. That would certainly be sufficient. Ok then Waldo gets it back. :-) |