[jira] [Updated] (TS-481) Poorly handled remap with proxy.config.url_remap.url_remap_mode set to 2

["Leif Hedstrom (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-481:
-----------------------------
    Summary: Poorly handled remap with proxy.config.url_remap.url_remap_mode set to 2  (was: Missing remap support for two cases)

> Poorly handled remap with proxy.config.url_remap.url_remap_mode set to 2
> ------------------------------------------------------------------------
>
>                 Key: TS-481
>                 URL: https://issues.apache.org/jira/browse/TS-481
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: HTTP
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>             Fix For: sometime
>
>
> There are two cases where the remap processor is not used, but it should. As of v2.1.4, the broken support was removed (broken code is worse than no code), making two cases not use / support "remap" features. Both cases currently call request_url_remap() which is now set to return false. The two cases are
> 1) If you configure remap mode to be URL_REMAP_FOR_OS (2). This is an undocumented feature, I don't even know when or why you'd want to use it. The setting in RecordsConfig.cc is proxy.config.url_remap.url_remap_mode, which defaults to "1".
> 2) If TS uses "raw" connections, I think for example when using the CONNECT method, we will not do remap rules. This would be in a forward proxy mode, primarily for things like HTTPS afaik.
> I don't think either case are critical to get support for the remap processor for v2.2, but please adjust the fix version if necessary.



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