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
It recently came to light that EDDN has a maximum accepted message size . If any message is larger than this then the sender will receive an HTTP 413 status code.
We need to ensure that we handle this sanely. In particular ensure that such a message (probably a large navroute) doesn't cause any subsequent EDDN messages to be blocked.
The text was updated successfully, but these errors were encountered:
This is a sidestep solution to EDCD#1390. It doesn't attempt to directly
resend data, only compressing with gzip over a given size. If that STILL
returns a 413, its dropped, as without introspection of the message we
cannot make it any smaller
This is a sidestep solution to EDCD#1390. It doesn't attempt to directly
resend data, only compressing with gzip over a given size. If that STILL
returns a 413, its dropped, as without introspection of the message we
cannot make it any smaller
A-UNDERSCORE-D
added a commit
to A-UNDERSCORE-D/EDMarketConnector
that referenced
this issue
Jan 26, 2022
This is a sidestep solution to EDCD#1390. It doesn't attempt to directly
resend data, only compressing with gzip over a given size. If that STILL
returns a 413, its dropped, as without introspection of the message we
cannot make it any smaller
It recently came to light that EDDN has a maximum accepted message size . If any message is larger than this then the sender will receive an HTTP
413
status code.We need to ensure that we handle this sanely. In particular ensure that such a message (probably a large
navroute
) doesn't cause any subsequent EDDN messages to be blocked.The text was updated successfully, but these errors were encountered: