[
https://issues.apache.org/jira/browse/DRILL-7626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061868#comment-17061868
]
Dmytro Kondriukov commented on DRILL-7626:
------------------------------------------
*Verified*
Test presence Response Headers:
* Content-Security-Policy: default-src https:; script-src 'unsafe-inline'
https:; style-src 'unsafe-inline' https:; font-src data: https:; img-src data:
https:
* Strict-Transport-Security: max-age=31536000;includeSubDomains
* X-Content-Type-Options: nosniff
* X-XSS-Protection: 1; mode=block
Check resources on pages:
* Login page
* Landing page
* /query
* /storage
* /metrics
* /threads
* /logs
* /options
* /logout
Test on:
Drill 1.18.0-SNAPSHOT commit 2f8dcb62f65a81510385173757bd33a93789d95a
found bug: DRILL-7648
> Add ability to set HTTP response headers
> ----------------------------------------
>
> Key: DRILL-7626
> URL: https://issues.apache.org/jira/browse/DRILL-7626
> Project: Apache Drill
> Issue Type: Sub-task
> Reporter: Igor Guzenko
> Assignee: Igor Guzenko
> Priority: Major
> Labels: ready-to-commit
> Fix For: 1.18.0
>
>
> It should be possible to make response headers configurable under common
> options path
> *drill.exec.http.jetty.server.response.headers*, like
> {code:none}
> jetty: {
> server: {
> response: {
> # any response headers with constant values may be configured like
> this
> headers: {
> "Custom Header Name": "Text Value",
> "BooleanHeader": true
> }
> }
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
