[
https://issues.apache.org/jira/browse/TS-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659547#comment-14659547
]
ASF GitHub Bot commented on TS-1232:
------------------------------------
Github user ushachar commented on the pull request:
https://github.com/apache/trafficserver/pull/270#issuecomment-128261744
I'm not too sure about this -- It's one thing to allow/block unknown
methods that parse properly (TS-1232/TS-1407), but adding non-HTTP methods to
the HTTP method list just for the ip-allow functionlity seems like another
thing that can be best accomplished in plugin space....
Some technical comments:
1) Maybe rename HTTP_WKSIDX_... -> WEBDAV_WKSIDX_...
2) Some WebDAV methods should be treated like POST in that they are
required to have payload (I don't think there's any method that's explicitly
forbidden from having payload).
3) Should we support the "If" header?
(http://www.webdav.org/specs/rfc4918.html#rfc.section.10.4.5)
> Support unknown methods in HTTP requests
> ----------------------------------------
>
> Key: TS-1232
> URL: https://issues.apache.org/jira/browse/TS-1232
> Project: Traffic Server
> Issue Type: Improvement
> Components: HTTP
> Affects Versions: 3.1.3
> Reporter: Uri Shachar
> Labels: http
> Fix For: 3.2.4
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> When acting as a transparent proxy, we may intercept WebDAV and other HTTP
> based protocols.
> Currently, the response will be "405 Method Not Allowed" even though ATS can
> deal with the request as long as the rest of it is well-formed.
> Adding this functionality requires only minor changes and it could be
> configured on/off (proxy.config.http.accept_unknown_methods)
> Interested?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
