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 (Updated) (JIRA)" <ji...@apache.org> on 2011/10/05 00:40:37 UTC

[jira] [Updated] (TS-481) Missing remap support for two cases

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

Leif Hedstrom updated TS-481:
-----------------------------

    Fix Version/s:     (was: 3.1.2)
                   3.2.0
    
> Missing remap support for two cases
> -----------------------------------
>
>                 Key: TS-481
>                 URL: https://issues.apache.org/jira/browse/TS-481
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: HTTP
>            Reporter: Leif Hedstrom
>             Fix For: 3.2.0
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira