[
https://issues.apache.org/jira/browse/TEZ-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013049#comment-16013049
]
Sreenath Somarajapuram commented on TEZ-3724:
---------------------------------------------
[~jeagles] Sorry for the delay.
Existing behavior:
1. If UI is running in HTTP, it force the REST URLs to start with HTTP.
2. If UI is running in HTTPS, it force the REST URLs to start with HTTPS.
3. If UI is running directly from local file system (file:). And if the REST
URLs come with no protocol it forces HTTP protocol.
The behavior is by design. Use-case of UI and REST APIs using two separate
protocols (HTTP/HTTPS) wasn't there until now. Moreover such a configuration
would cause CORS issues. Hence it was forced by design to use the same protocol.
- But now, as we have CORS support everywhere & better error bars in place,
guess its fine to go this way. And for that you would just have to remove the
"urlProto = localProto;" line.
> Tez UI on HTTP "corrects" HTTPS REST calls to HTTP
> --------------------------------------------------
>
> Key: TEZ-3724
> URL: https://issues.apache.org/jira/browse/TEZ-3724
> Project: Apache Tez
> Issue Type: Bug
> Components: UI
> Reporter: Jonathan Eagles
> Assignee: Jonathan Eagles
> Attachments: TEZ-3724.1.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
