Uh oh!
There was an error while loading. Please reload this page.
[SPARK-19220][UI] Make redirection to HTTPS apply to all URIs. (branch-2.1) - #16711
Closed
vanzin wants to merge 1 commit into
Closed
[SPARK-19220][UI] Make redirection to HTTPS apply to all URIs. (branch-2.1)#16711vanzin wants to merge 1 commit into
vanzin wants to merge 1 commit into
Conversation
The redirect handler was installed only for the root of the server; any other context ended up being served directly through the HTTP port. Since every sub page (e.g. application UIs in the history server) is a separate servlet context, this meant that everything but the root was accessible via HTTP still. The change adds separate names to each connector, and binds contexts to specific connectors so that content is only served through the HTTPS connector when it's enabled. In that case, the only thing that binds to the HTTP connector is the redirect handler. Tested with new unit tests and by checking a live history server. Author: Marcelo Vanzin <vanzin@cloudera.com> Closesapache#16582 from vanzin/SPARK-19220. (cherry picked from commit d3dcb63)
SparkQA
commented
Jan 26, 2017
Test build #72031 has finished for PR 16711 at commit
|
vanzin
commented
Jan 26, 2017
ContributorAuthor
retest this please |
SparkQA
commented
Jan 27, 2017
Test build #72049 has finished for PR 16711 at commit
|
vanzin
commented
Jan 27, 2017
ContributorAuthor
Merging to 2.1 (and 2.0 if no conflicts). |
asfgit pushed a commit
that referenced
this pull request
Jan 27, 2017
…h-2.1) The redirect handler was installed only for the root of the server; any other context ended up being served directly through the HTTP port. Since every sub page (e.g. application UIs in the history server) is a separate servlet context, this meant that everything but the root was accessible via HTTP still. The change adds separate names to each connector, and binds contexts to specific connectors so that content is only served through the HTTPS connector when it's enabled. In that case, the only thing that binds to the HTTP connector is the redirect handler. Tested with new unit tests and by checking a live history server. (cherry picked from commit d3dcb63) Author: Marcelo Vanzin <vanzin@cloudera.com> Closes#16711 from vanzin/SPARK-19220_2.1.
vanzin
commented
Jan 27, 2017
ContributorAuthor
Didn't merge to 2.0. |
This file contains hidden or 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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 redirect handler was installed only for the root of the server;
any other context ended up being served directly through the HTTP
port. Since every sub page (e.g. application UIs in the history
server) is a separate servlet context, this meant that everything
but the root was accessible via HTTP still.
The change adds separate names to each connector, and binds contexts
to specific connectors so that content is only served through the
HTTPS connector when it's enabled. In that case, the only thing that
binds to the HTTP connector is the redirect handler.
Tested with new unit tests and by checking a live history server.
(cherry picked from commit d3dcb63)