#1596 Prosody includes Content-Length header on inappropriate responses

Reporter MattJ
Owner MattJ
Created
Updated
Stars ★ (1)
Tags
  • Status-Fixed
  • Priority-Medium
  • Milestone-0.11
  • Type-Defect
  1. MattJ on

    What steps will reproduce the problem? 1. Initiate a websocket handshake with Prosody 2. Prosody returns a `101 Switching Protocols` response What is the expected output? According to RFC 7230, responses with a 1xx or 204 code MUST NOT be served with a content-length header. What do you see instead? Prosody sets `Content-Length: 0`. This is seemingly ignored by many implementations, but fails with some reverse proxies (they close the connection) and possibly some client libraries (including .NET's websocket library). What version of the product are you using? On what operating system? Prosody 0.11.7.

  2. MattJ on

    Changes
    • tags Milestone-0.11
  3. MattJ on

    Fixed in https://hg.prosody.im/trunk/rev/de76f566159e

    Changes
    • tags Status-Fixed
    • owner MattJ

New comment

Not published. Used for spam prevention and optional update notifications.