Hi there Under graylog-1.3.4 I had published graylog-web behind a WAF - which nicely mapped https://graylog.internet.domain to http://graylog.intranet.domain (notice the different domain names too)
With v2.0 I can't get this to work. Now it appears graylog returns content with hardwired URLs that are defined by rest_listen_uri? That means we end up with browser errors as they are talking to the WAF over HTTPS and the content contains HTTP links - to port 12900. Bad. Am I correct that graylog-v2 requires browsers to talk to non-web ports (ie 12900)? That's quite a change. The comments say "Must be reachable by other Graylog server nodes if you run a cluster" - no mention of this being required by web browsers. I'm confused? -- Cheers Jason Haar Information Security Manager, Trimble Navigation Ltd. Phone: +1 408 481 8171 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 -- 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/CAFChrgL8SC3ZoxkB2k4A_QsAsiy3a_rwO%2BamDYHdLJPK-4Ww_A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
