https://bugs.kde.org/show_bug.cgi?id=507265
--- Comment #10 from Robby Stephenson <ro...@periapsis.org> --- The pointer was helpful. I did confirm that the Content-Length: 0 header is being sent, in contrast to curl and even when using QNetworkAccessManager/QNetworkRequest directly. RFC9110, https://www.rfc-editor.org/rfc/rfc9110.html#name-content-length, says: > A user agent SHOULD NOT send a Content-Length header field when the request > message does not contain content > and the method semantics do not anticipate such data. An older one, RFC2616, https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.13, is worded differently. > Any Content-Length greater than or equal to zero is a valid value. There doesn't seem to be anything that distinguishes method semantics in the older RFC. I'll try to pull together a separate bug report against KIO and also see if there's a workaround that Tellico could do to block the header form being included. From my quick glance through the code, I didn't see one (nor actually where the Content-Length header is even being set for the GET request). There are various reports around the web of this being an issue for some CDNs. https://github.com/http-kit/http-kit/issues/583 https://github.com/httprb/http/issues/487 In the meantime, the brgbib server seems to work with SRU POST requests. I've now added support for specifying a POST request for the next Tellico release. -- You are receiving this mail because: You are watching all bug changes.
