-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
API browser should use relative links #1576
Comments
+1 for getting this fixed. API browser is currently not working behind proxy. Swagger has options to change the UI path, see options.apiDocs and options.swaggerUi in https://github.com/apigee-127/swagger-tools/blob/master/docs/Middleware.md. |
I know this is quite old. @jalogisch kindly referenced me to this ticket. |
Any chance this is going to be fixed soon? Would be nice to be able to explore the API behind a reverse proxy. |
I'm a bit surprised that this issue still wasn't fixed in Graylog 6.0. If you're using Nginx, here's one way to fix it using http_sub_module: location ~ ^/api/api-(browser/$|docs/) {
proxy_set_header Accept-Encoding "";
sub_filter 'http://<Your Node IP>:80/' '$scheme://$host/';
sub_filter_once off;
sub_filter_types text/html application/json;
proxy_pass http://<Your Node IP>;
} |
It seems like certain proxy setups have problems with the links the API browser code generates.
Since this is adapted Swagger code we don't have direct control over it, investigate if we can update the version or tweak it so that proxy support is actually possible.
The text was updated successfully, but these errors were encountered: