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/02/04 19:55:51 UTC

[jira] [Closed] (TS-3723) Failed remap shouldn't log as ERR_CONNECT_FAIL

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

Leif Hedstrom closed TS-3723.
-----------------------------

> Failed remap shouldn't log as ERR_CONNECT_FAIL
> ----------------------------------------------
>
>                 Key: TS-3723
>                 URL: https://issues.apache.org/jira/browse/TS-3723
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core, Logging
>            Reporter: Brian Geffon
>            Assignee: Brian Geffon
>             Fix For: 6.0.0
>
>
> It appears that upon a failed remap (when remap is required) it is logged as ERR_CONNECT_FAIL, this is confusing as no connection attempt was actually made. ERR_INVALID_URL makes more sense as remap was required so technically this is an invalid URL. Nothing else will change the response code will still be 404 with the mapping failed body factory page.



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