You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2016/06/30 02:02:12 UTC

[jira] [Commented] (TS-4405) Remove proxy.config.http.parse.allow_non_http ?

    [ https://issues.apache.org/jira/browse/TS-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356325#comment-15356325 ] 

Leif Hedstrom commented on TS-4405:
-----------------------------------

Now, the questions are:

1) Do we need to keep this option?

2) Is the default “1” actually reasonable? If we disabled it, what would we break? Anything?

3) If we removed the option, do we make the logic assume the current “1” behavior, or the “0” behavior?


> Remove proxy.config.http.parse.allow_non_http ?
> -----------------------------------------------
>
>                 Key: TS-4405
>                 URL: https://issues.apache.org/jira/browse/TS-4405
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Configuration, HTTP
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>             Fix For: 7.0.0
>
>
> This option, undocumented, seems pretty useless. As far as I can tell, it allows the HTTP response to exclude e.g. HTTP/1.1. Does anyone actually use / need this ? Seems that enabling would cause more harm than good?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)