You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The value for maximum size of headers returned by an origin is currently hardcoded to 8192 bytes.
Detailed description
Currently Styx rejects any response from an origin whenever the header size is larger than 8192 bytes without any option to configure the max header size for received responses.
There is a parameter maxHeaderSize that allows configuring the maximum header size for requests received by styx-server, but there is no equivalent configuration for the client side (outgoing connection to the origins) and the default value is always used.
The text was updated successfully, but these errors were encountered:
dvlato
changed the title
maxHeaderSize not configurable for the client side
maxHeaderSize not configurable for responses received from origins
Jan 28, 2020
dvlato
pushed a commit
to dvlato/styx
that referenced
this issue
Jan 28, 2020
dvlato
changed the title
maxHeaderSize not configurable for responses received from origins
maximum header size not configurable for responses received from origins
Jan 29, 2020
The problem
The value for maximum size of headers returned by an origin is currently hardcoded to 8192 bytes.
Detailed description
Currently Styx rejects any response from an origin whenever the header size is larger than 8192 bytes without any option to configure the max header size for received responses.
There is a parameter
maxHeaderSize
that allows configuring the maximum header size for requests received by styx-server, but there is no equivalent configuration for the client side (outgoing connection to the origins) and the default value is always used.The text was updated successfully, but these errors were encountered: