Determine management app context path dynamically #1095
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I stumbled upon this issue while testing the management webapp on heroku. |
|
+1 |
mmoayyed
pushed a commit
that referenced
this pull request
Aug 18, 2015
Determine management app context path dynamically
|
Heroku demos now fully functional |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The management webapp assumes a static
cas-managementcontext path. This is not true everywhere, because the app can take on any context path, or none if it's deployed at the root. This pull dynamically determines what the path is going to be, and adjusts AJAX calls accordingly.