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

Graylog 2.0 web server - Unable to specify application context #2191

Closed
libby2cm opened this Issue May 4, 2016 · 0 comments

Comments

Projects
None yet
3 participants
@libby2cm

libby2cm commented May 4, 2016

Problem description

In GL 2.0, an application context specified in 'web_listen_uri' is not honored.

Steps to reproduce the problem

  1. Set 'web_listen_uri' to something like http://0.0.0.0:9000/graylog and it doesn't work.. site does bind to that URI, but all artifact paths are not re-written and remain at the root level, rather than out of the web context, so the page will not load. This causes an issue on a shared hostname I have, where I route requests out of nginx from based on web context. In graylog 1.x, you could specify the setting 'application.context' for this, but that setting has been removed from 2.0.

Environment

  • Graylog Version: 2.0
  • Elasticsearch Version: 2.0
  • MongoDB Version: 2.6.4
  • Operating System: OEL 6.7
  • Browser version: chrome/ie 11

@dennisoelkers dennisoelkers self-assigned this May 9, 2016

@kroepke kroepke added bug S3 P3 labels May 9, 2016

dennisoelkers added a commit that referenced this issue May 10, 2016

@joschi joschi closed this in #2208 May 10, 2016

joschi added a commit that referenced this issue May 10, 2016

joschi added a commit that referenced this issue May 10, 2016

@kroepke kroepke added the triaged label Sep 21, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment