Skip to content
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

[Bug Fix] Forward response headers so front end can correctly handle content-encoding #99

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

hyperevo
Copy link

@hyperevo hyperevo commented May 8, 2024

The pulsar REST api returns data that is gzip encoded. The front end needs to see the content-encoding header in order to decode the data. Previously the content-encoding header was not forwarded to the front end and it did not do this which caused it to malfunction. I added some code in the proxy that forwards the api response headers to the front end and now the front end correctly decodes the response data.

I also added another fix that returns error 500 if the proxy encounters an unknown error when trying to make the request. Previously it would crash because it was trying to access the status property that didn't exist.

…handle content-encoding. Also added a 500 response code when the response doesnt exist
@brunocascio
Copy link

Please, merge this :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants