[jira] [Updated] (TEZ-3966) Tez UI config couldn't be executed in browser
[ https://issues.apache.org/jira/browse/TEZ-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated TEZ-3966: - Attachment: simple-cors-http-server.py > Tez UI config couldn't be executed in browser > -- > > Key: TEZ-3966 > URL: https://issues.apache.org/jira/browse/TEZ-3966 > Project: Apache Tez > Issue Type: Bug > Components: UI >Reporter: Roman Lukin >Priority: Major > Attachments: Selection_043.png, Selection_044.png, > simple-cors-http-server.py > > > Current name convention applied to the ui configuration file, produce the > following error in web browser - mime type check fails (which based on file > extesion) and if header `X-Content-Type-Options: nosniff` enabled config > wouldn't be executed and used. As a result we may have problems, for instance > links based on variable `yarnProtocol`. > More about header - > [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] > Possible solution - rename file `config.env` to `config.js` > [https://github.com/apache/tez/pull/26] > [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] > > Steps to reproduce: > * Enable aforementioned header on web server > * Try to load tez ui -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEZ-3966) Tez UI config couldn't be executed in browser
[ https://issues.apache.org/jira/browse/TEZ-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Lukin updated TEZ-3966: - Description: Current name convention applied to the ui configuration file, produce the following error in web browser - mime type check fails (which based on file extesion) and if header `X-Content-Type-Options: nosniff` enabled config wouldn't be executed and used. As a result we may have problems, for instance links based on variable `yarnProtocol`. More about header - [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] Possible solution - rename file `config.env` to `config.js` [https://github.com/apache/tez/pull/26] [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] Steps to reproduce: * Enable aforementioned header on web server * Try to load tez ui was: Current name convention applied to the ui configuration file, produce the following error in web browser - mime type check fails (which based on file extesion) and if header `X-Content-Type-Options: nosniff` enabled config wouldn't be executed and used. As a result we may have problems, for instance links based on variable `yarnProtocol`. More about header - [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] Possible solution - rename file `config.env` to `config.js` [https://github.com/apache/tez/pull/26] [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] Steps to reproduce: * Enable header on web server * Try to load tez ui > Tez UI config couldn't be executed in browser > -- > > Key: TEZ-3966 > URL: https://issues.apache.org/jira/browse/TEZ-3966 > Project: Apache Tez > Issue Type: Bug > Components: UI >Reporter: Roman Lukin >Priority: Major > Attachments: Selection_043.png, Selection_044.png > > > Current name convention applied to the ui configuration file, produce the > following error in web browser - mime type check fails (which based on file > extesion) and if header `X-Content-Type-Options: nosniff` enabled config > wouldn't be executed and used. As a result we may have problems, for instance > links based on variable `yarnProtocol`. > More about header - > [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] > Possible solution - rename file `config.env` to `config.js` > [https://github.com/apache/tez/pull/26] > [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] > > Steps to reproduce: > * Enable aforementioned header on web server > * Try to load tez ui -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEZ-3966) Tez UI config couldn't be executed in browser
[ https://issues.apache.org/jira/browse/TEZ-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Lukin updated TEZ-3966: - Description: Current name convention applied to the ui configuration file, produce the following error in web browser - mime type check fails (which based on file extesion) and if header `X-Content-Type-Options: nosniff` enabled config wouldn't be executed and used. As a result we may have problems, for instance links based on variable `yarnProtocol`. More about header - [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] Possible solution - rename file `config.env` to `config.js` [https://github.com/apache/tez/pull/26] [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] Steps to reproduce: * Enable header on web server * Try to load tez ui was: Current name convention applied to the ui configuration file, produce the following error in web browser - mime type check fails (which based on file extesion) and if header `X-Content-Type-Options: nosniff` enabled config wouldn't be executed and used. As a result we may have problems, for instance links based on variable `yarnProtocol`. More about header - [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] Possible solution - rename file `config.env` to `config.js` [https://github.com/apache/tez/pull/26] [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] Steps to reproduce: * Enable header on web server * Try to load tez ui * !Selection_043.png! > Tez UI config couldn't be executed in browser > -- > > Key: TEZ-3966 > URL: https://issues.apache.org/jira/browse/TEZ-3966 > Project: Apache Tez > Issue Type: Bug > Components: UI >Reporter: Roman Lukin >Priority: Major > Attachments: Selection_043.png, Selection_044.png > > > Current name convention applied to the ui configuration file, produce the > following error in web browser - mime type check fails (which based on file > extesion) and if header `X-Content-Type-Options: nosniff` enabled config > wouldn't be executed and used. As a result we may have problems, for instance > links based on variable `yarnProtocol`. > More about header - > [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] > Possible solution - rename file `config.env` to `config.js` > [https://github.com/apache/tez/pull/26] > [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] > > Steps to reproduce: > * Enable header on web server > * Try to load tez ui -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEZ-3966) Tez UI config couldn't be executed in browser
[ https://issues.apache.org/jira/browse/TEZ-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Lukin updated TEZ-3966: - Description: Current name convention applied to the ui configuration file, produce the following error in web browser - mime type check fails (which based on file extesion) and if header `X-Content-Type-Options: nosniff` enabled config wouldn't be executed and used. As a result we may have problems, for instance links based on variable `yarnProtocol`. More about header - [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] Possible solution - rename file `config.env` to `config.js` [https://github.com/apache/tez/pull/26] [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] Steps to reproduce: * Enable header on web server * Try to load tez ui * !Selection_043.png! was: Current name convention applied to the ui configuration file, produce the following error in web browser - mime type check fails (which based on file extesion) and if we enable header `X-Content-Type-Options: nosniff` config wouldn't be executed and used. As a result we may have problems, for instance links based on variable `yarnProtocol`. More about header - [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] Possible solution - rename file `config.env` to `config.js` [https://github.com/apache/tez/pull/26] [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] Steps to reproduce: * Enable header on web server * Try to load tez ui * !Selection_043.png! > Tez UI config couldn't be executed in browser > -- > > Key: TEZ-3966 > URL: https://issues.apache.org/jira/browse/TEZ-3966 > Project: Apache Tez > Issue Type: Bug > Components: UI >Reporter: Roman Lukin >Priority: Major > Attachments: Selection_043.png, Selection_044.png > > > Current name convention applied to the ui configuration file, produce the > following error in web browser - mime type check fails (which based on file > extesion) and if header `X-Content-Type-Options: nosniff` enabled config > wouldn't be executed and used. As a result we may have problems, for instance > links based on variable `yarnProtocol`. > More about header - > [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] > Possible solution - rename file `config.env` to `config.js` > [https://github.com/apache/tez/pull/26] > [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] > > Steps to reproduce: > * Enable header on web server > * Try to load tez ui > * !Selection_043.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
