-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bad request returns invalid gzip compressed data #656
Comments
fengelniederhammer
added
bug
Something isn't working
LAPIS
Tasks/PR related to LAPIS
labels
Feb 20, 2024
fengelniederhammer
changed the title
bad request - compressed
bad request returns invalid gzip compressed data
Feb 20, 2024
fengelniederhammer
added a commit
that referenced
this issue
Feb 20, 2024
Apparently the following happened: * The gzip stream eagerly writes the gzip header to the underlying stream (in its constructor) * an error occurs * Spring's error handling resets the response buffer (erasing the gzip header) * The exception handler writes a messages, which gets gzip compressed. Fix by: Delay initializing the gzip output stream until something is written to it.
Observations:
|
fengelniederhammer
added a commit
that referenced
this issue
Feb 20, 2024
Apparently the following happened: * The gzip stream eagerly writes the gzip header to the underlying stream (in its constructor) * an error occurs * Spring's error handling resets the response buffer (erasing the gzip header) * The exception handler writes a messages, which gets gzip compressed. Fix by: Delay initializing the gzip output stream until something is written to it.
1 task
fengelniederhammer
added a commit
that referenced
this issue
Feb 20, 2024
Apparently the following happened: * The gzip stream eagerly writes the gzip header to the underlying stream (in its constructor) * an error occurs * Spring's error handling resets the response buffer (erasing the gzip header) * The exception handler writes a messages, which gets gzip compressed. Fix by: Delay initializing the gzip output stream until something is written to it.
fengelniederhammer
added a commit
that referenced
this issue
Feb 21, 2024
Apparently the following happened: * The gzip stream eagerly writes the gzip header to the underlying stream (in its constructor) * an error occurs * Spring's error handling resets the response buffer (erasing the gzip header) * The exception handler writes a messages, which gets gzip compressed. Fix by: Delay initializing the gzip output stream until something is written to it.
This was referenced May 6, 2024
Merged
Merged
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Apparently, when SILO returns a 400 and LAPIS was requested to return compressed data, LAPIS sends out compressed data, but not the corresponding header. Investigate and eventually fix.
The text was updated successfully, but these errors were encountered: