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
I'm not sure yet why this is happening but when I serve my Swagger UI with this plugin via AWS API Gateway, it displays incorrectly - I see a page of garbled binary characters. Everything works fine when I run Hapi locally though. When I curl the endpoint I receive valid HTML however if I add this header "Accept-Encoding: gzip, deflate, br" to my curl command, I see the ame behavior.
Interestingly, the behavior is similar to hapi-swagger/hapi-swagger#528 which makes me wonder if this isn't a problem in the underlying hapi library itself.
Any help is appreciated.
The text was updated successfully, but these errors were encountered:
I'm not sure yet why this is happening but when I serve my Swagger UI with this plugin via AWS API Gateway, it displays incorrectly - I see a page of garbled binary characters. Everything works fine when I run Hapi locally though. When I curl the endpoint I receive valid HTML however if I add this header
"Accept-Encoding: gzip, deflate, br"
to my curl command, I see the ame behavior.Interestingly, the behavior is similar to hapi-swagger/hapi-swagger#528 which makes me wonder if this isn't a problem in the underlying hapi library itself.
Any help is appreciated.
The text was updated successfully, but these errors were encountered: