I've just figured out how to get my reverse proxy working properly to fully support the web client, but it leads me to another dilemma. When the JS application loads, it tries to talk to the REST API URI rather than just the Web API URI. This poses a problem when I want to publicly expose and proxy the web interface, but not the main rest interface (or vice versa). I have to set both the web_endpoint_uri and rest_transport_uri to the same domain due to use of https. This means that all of my graylog nodes are going to try and connect to my public IP which is then handled by my reverse proxy and has to redistribute again - which causes an unnecessary resource bottleneck on my main node running the reverse proxy.
So my feature request is that the JS client only ever talks to the api via web_endpoint_uri. That way the web and rest can be setup for different use cases. Thanks -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/a9e4a5ab-4dd3-47d8-9bc3-a60d48f16448%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
