[Webkit-unassigned] [Bug 31140] [Qt] Allow setting HTTP headers with empty value in XMLHTTPRequest

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Nov 5 08:29:18 PST 2009


https://bugs.webkit.org/show_bug.cgi?id=31140





--- Comment #3 from Yael <yael.aharon at nokia.com>  2009-11-05 08:29:17 PDT ---
(In reply to comment #2)
> Hm, we should talk to Thiago about this. Clearly calling setRawHeader() with a
> null value is currently the only way to _remove_ a header field from a request.
> But I think it would be cleaner if QNetworkRequest had a removeRawHeader()
> function and would allow empty header values.
> 
> Your use-case is a good example of why supporting it would make sense, and
> therefore it would be nice to not have to work around Qt's behaviour in WebKit
> if possible.
> 
> But yes, the last resort is your patch, which looks fine otherwise :)

Simon, I completely agree with you that this is a workaround for a QtNetwork
issue. However, if we change QtNetwork, we will break its backwards
compatibility, and I did not think Thiago will agree to that.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list