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
There seems to still be an issue with using Plack behind nginx when firefox aborts connections, Seems something on the plack side spins on the socket and never closes, can confirm that its only when firefox calls abort, adding an Expires 0 header prevents firefox from doing this behavior which is related to client caching.
Where should I focus my efforts to properly catch and address this situation, seems as if its a nice attack vector for a denial of service.
The text was updated successfully, but these errors were encountered:
There seems to still be an issue with using Plack behind nginx when firefox aborts connections, Seems something on the plack side spins on the socket and never closes, can confirm that its only when firefox calls abort, adding an Expires 0 header prevents firefox from doing this behavior which is related to client caching.
Where should I focus my efforts to properly catch and address this situation, seems as if its a nice attack vector for a denial of service.
The text was updated successfully, but these errors were encountered: