subject:"\[jira\] \[Commented\] \(TS\-2344\) 404 error was logged while url redirect request was processed corrctly"

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-05-25 Thread Ethan Lai (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008477#comment-14008477
 ] 

Ethan Lai commented on TS-2344:
---

[~bcall] It seems the 
proxy/config/body_factory/default/redirect#moved_permanently response file is 
not added, please commit this file as well. (Copied from 
proxy/config/body_factory/default/redirect#moved_temporary)  :)

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Bryan Call
  Labels: Review
 Fix For: 5.0.0

 Attachments: no_redirect_after_map.patch


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-05-23 Thread Bryan Call (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1400#comment-1400
 ] 

Bryan Call commented on TS-2344:


Looking at the latest patch.  A would like to get rid of the new location in 
the response entirely.   Please ping me directly if you would like details.  I 
will update the patch and commit it.

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Bryan Call
  Labels: Review
 Fix For: 5.0.0

 Attachments: no_redirect_after_map.patch


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-05-23 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007813#comment-14007813
 ] 

ASF subversion and git services commented on TS-2344:
-

Commit 0d6042581140349c75446ec214bfc0274ee9f4fb in trafficserver's branch 
refs/heads/master from [~bcall]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=0d60425 ]

TS-2344: 404 error was logged while url redirect request was processed corrctly
Reviewed: Bryan Call


 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Bryan Call
  Labels: Review
 Fix For: 5.0.0

 Attachments: no_redirect_after_map.patch


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-05-23 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007822#comment-14007822
 ] 

ASF subversion and git services commented on TS-2344:
-

Commit b8a647dc30d3a66ac270cd306876a31d7a86b372 in trafficserver's branch 
refs/heads/master from [~bcall]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=b8a647d ]

TS-2344: fixed problem with freeing the string


 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Bryan Call
  Labels: Review
 Fix For: 5.0.0

 Attachments: no_redirect_after_map.patch


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-05-17 Thread Ethan Lai (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14000683#comment-14000683
 ] 

Ethan Lai commented on TS-2344:
---

The remap_redirect URL is used inside of build_error_response(), which set 
correct Location header for building response body with %{Location}psh 
field.
If this Location header is set after calling build_error_response(), response 
body will have empty %{Location}psh field because it was already generated.
{code}
+  if ((status_code == HTTP_STATUS_TEMPORARY_REDIRECT ||
+   status_code == HTTP_STATUS_MOVED_TEMPORARILY ||
+   status_code == HTTP_STATUS_MOVED_PERMANENTLY) 
+  s-remap_redirect) {
+s-hdr_info.client_response.value_set(MIME_FIELD_LOCATION, 
MIME_LEN_LOCATION, s-remap_redirect, strlen(s-remap_redirect));
+  }
{code}

I'm not that familiar with passing additional parameter, remap_redirect_len 
here, while calling build_error_response().
Please feel free to enhance this patch. :)

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Leif Hedstrom
  Labels: Review
 Fix For: 5.0.0

 Attachments: no_redirect_after_map.patch


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-05-16 Thread Leif Hedstrom (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998890#comment-13998890
 ] 

Leif Hedstrom commented on TS-2344:
---

This turns out to be a huge PITA to merge, because your branch is so far behind 
master, it gets conflicts on unrelated stuff :-/. I'll try to manually merge 
it, alternatively, do one of

1. Keep your branch(es) up to date.

2. Attach the diff to this Jira.

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Leif Hedstrom
  Labels: Review
 Fix For: 5.0.0

 Attachments: no_redirect_after_map.patch


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-05-16 Thread Ethan Lai (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13999459#comment-13999459
 ] 

Ethan Lai commented on TS-2344:
---

[~zwoop] Just as I wrote on 04/Mar:
1. Class URL(redirect_url) is not holding a NULL terminated string, just get 
its reference might cause thereafter MIME_FIELD_LOCATION length, 
strlen(s-remap_redirect), mis-counted.

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Leif Hedstrom
  Labels: Review
 Fix For: 5.0.0

 Attachments: no_redirect_after_map.patch


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-05-16 Thread Leif Hedstrom (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1351#comment-1351
 ] 

Leif Hedstrom commented on TS-2344:
---

So what about the change in the URL string. Why is that necessary ? It seems 
like it sneaked in there, unrelated to this bug?

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Leif Hedstrom
  Labels: Review
 Fix For: 5.0.0

 Attachments: no_redirect_after_map.patch


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-05-16 Thread Leif Hedstrom (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14000313#comment-14000313
 ] 

Leif Hedstrom commented on TS-2344:
---

Huh. So why not save the length away with the string ? You get it with 
string_get_ref().

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Leif Hedstrom
  Labels: Review
 Fix For: 5.0.0

 Attachments: no_redirect_after_map.patch


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-05-16 Thread Leif Hedstrom (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998898#comment-13998898
 ] 

Leif Hedstrom commented on TS-2344:
---

Ok, so reading this last set of diffs, why is this necessary:

-remap_redirect = redirect_url.string_get_ref(remap_redirect_len);
+s-remap_redirect = redirect_url.string_get(NULL, remap_redirect_len);
+redirect_url.destroy();



This seems like a significant degradation in performance.

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Leif Hedstrom
  Labels: Review
 Fix For: 5.0.0

 Attachments: no_redirect_after_map.patch


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-05-15 Thread Ethan Lai (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998303#comment-13998303
 ] 

Ethan Lai commented on TS-2344:
---

Sorry, do not notice that constant changed in 5.x.
I've committed the new change, please take a look again.

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Leif Hedstrom
  Labels: Review
 Fix For: 5.0.0

 Attachments: no_redirect_after_map.patch


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-05-15 Thread Leif Hedstrom (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997683#comment-13997683
 ] 

Leif Hedstrom commented on TS-2344:
---

That branch does not build for me, PROXY_INTERNAL_CACHE_NOOP is not defined.

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Leif Hedstrom
  Labels: Review
 Fix For: 5.0.0

 Attachments: no_redirect_after_map.patch


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-05-13 Thread Leif Hedstrom (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996460#comment-13996460
 ] 

Leif Hedstrom commented on TS-2344:
---

[~yzlai]

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Leif Hedstrom
  Labels: Review
 Fix For: 5.0.0

 Attachments: no_redirect_after_map.patch


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-05-13 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997104#comment-13997104
 ] 

ASF GitHub Bot commented on TS-2344:


GitHub user yzlai opened a pull request:

https://github.com/apache/trafficserver/pull/86

TS-2344 fix remap type redirect logging  response_body

* handleIfRedirect() should be called before 404 response and only if 
url_remap failed
* Location header should be added before build_error_response
* status_code  400 not logged

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yzlai/trafficserver TS-2344

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/trafficserver/pull/86.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #86


commit db002f0235d59167d15c76eaf2483971a6cecd40
Author: Ethan Lai yz...@yahoo.com
Date:   2014-05-14T00:23:26Z

TS-2344 fix remap type redirect logging  response_body

* handleIfRedirect() should be called before 404 response and only if 
url_remap failed
* Location header should be added before build_error_response
* status_code  400 not logged




 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Leif Hedstrom
  Labels: Review
 Fix For: 5.0.0

 Attachments: no_redirect_after_map.patch


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-05-13 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997096#comment-13997096
 ] 

ASF GitHub Bot commented on TS-2344:


Github user yzlai closed the pull request at:

https://github.com/apache/trafficserver/pull/40


 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Leif Hedstrom
  Labels: Review
 Fix For: 5.0.0

 Attachments: no_redirect_after_map.patch


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-04-06 Thread Ethan Lai (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13961581#comment-13961581
 ] 

Ethan Lai commented on TS-2344:
---

[~zwoop] Wondering a mapped request being matched and redirected is expected or 
not.
If not, current handleIfRedirect() call after and outside of 
(!s-url_remap_success) test will cause mapped requests being redirected.

As I know, map rules have type precedence. And current traffic server doesn't 
map target to replacement recursively.
However, after a successful map rule, another (regex_)redirect rule still take 
effect.  Just wondering is this expected behavior or not?
I'd want traffic server to be my SSL termination, and I'd also redirect non-SSL 
requests to SSL URLs.
With following remap.config, the final response will be HTTP 301 with 
https://real-www.test.example.com Location header.
  map https://www.example.com/   http://real-www.example.com/
  regex_redirect http://([\w\.\-]+)\.abc.com/  https://$1.abc.com/
Since remap rules are first matched, would it be better to stop redirect match 
after a success map?

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Leif Hedstrom
  Labels: Review
 Fix For: 5.0.0

 Attachments: no_redirect_after_map.patch


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-03-27 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13949586#comment-13949586
 ] 

ASF GitHub Bot commented on TS-2344:


Github user jpeach commented on the pull request:

https://github.com/apache/trafficserver/pull/40#issuecomment-38830876
  
ball is reviewing this patch in 
https://issues.apache.org/jira/browse/TS-2344


 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Bryan Call
  Labels: Review
 Fix For: 5.2.0


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-03-27 Thread Leif Hedstrom (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13950051#comment-13950051
 ] 

Leif Hedstrom commented on TS-2344:
---

Fwiw, I see the same problem in my logs. Besides this being wrong, why do we 
even log redirects in the error log? That makes no sense to me.

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Bryan Call
  Labels: Review
 Fix For: 5.0.0


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-03-04 Thread Ethan Lai (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919467#comment-13919467
 ] 

Ethan Lai commented on TS-2344:
---

[~bcall]
1. Class URL(redirect_url) is not holding a NULL terminated string, just get 
its reference might cause thereafter MIME_FIELD_LOCATION length, 
strlen(s-remap_redirect), mis-counted.
2. s-hdr_info.client_response is not built till build_response() call, #8111, 
inside build_error_response().  If set MIME_FIELD_LOCATION before calling 
build_error_response(), it causes segfault.
3.
  Current implementation will lookup with no mappings and build Not Found on 
Accelerator(#915) error response first, then call handleIfRedirect().  This is 
why there are 2 error logs which 404 first and 30x followed.
  My patch will call handleIfRedirect() right after !s-url_remap_success.  If 
this is a redirect request, the Not Found case will not be reached.  This 
prevents producing 404 error log.  Furthermore, since the error logs were 
produced inside build_error_response(), I thought redirect responses were not 
errors and error logs are not needed.
  About the MIME_FIELD_LOCATION setting, this MIME field must be set before 
calling body_factory-fabricate_with_old_api(), #8176.  Or the %{Location}psh 
field in response body will be empty.  This is another reason I move setting 
the location header into build_error_response().

Thanks,
-Ethan

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Bryan Call
  Labels: Review
 Fix For: 5.2.0


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-03-03 Thread Bryan Call (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917889#comment-13917889
 ] 

Bryan Call commented on TS-2344:


Is there are reason you are copying the url string out of the url object and 
having to deal with memory allocation yourself?
Why do you delay setting the location header until the build_error_response()?
Can you please describe the logic with the changes?

Thank you...


 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Bryan Call
  Labels: Review
 Fix For: 5.2.0


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2014-02-12 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898909#comment-13898909
 ] 

ASF GitHub Bot commented on TS-2344:


GitHub user yzlai opened a pull request:

https://github.com/apache/trafficserver/pull/40

TS-2344 fix remap type redirect logging  response_body

TS-2344 fix remap type redirect logging  response_body

* handleIfRedirect() should be called before 404 response
* Location header should be added before build_error_response
* status_code  400 not logged

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apache/trafficserver master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/trafficserver/pull/40.patch


commit 63832db235d09c830daea27a6a0c3f755ee19aff
Author: Ethan Lai yz...@yahoo.com
Date:   2014-02-12T08:03:02Z

TS-2344 fix remap type redirect logging  response_body




 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Bryan Call
 Fix For: 5.1.0


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2013-12-17 Thread Eddie (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850521#comment-13850521
 ] 

Eddie commented on TS-2344:
---

I am not working for Yahoo. You should not be able to connect to my server 
directly. But if we can set up a time, I can setup join.me for you to track 
down the problem. I have following line in my remap.config:

redirect http://yahoo.com http://www.yahoo.com

Following is how I made the request (and I did get back what I wanted to see):

curl -SIH HOST: yahoo.com http://68.87.98.110
HTTP/1.1 301 Redirect
Date: Tue, 17 Dec 2013 14:44:55 GMT
Server: ATS/3.2.4
Cache-Control: no-store
Content-Type: text/html
Content-Language: en
Connection: close
Location: http://www.yahoo.com/
Content-Length: 322


 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Bryan Call
 Fix For: sometime


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2013-12-16 Thread Bryan Call (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13849776#comment-13849776
 ] 

Bryan Call commented on TS-2344:


If you work for yahoo then please ping me on IM or send me an email.  I can 
jump on your server and help you track down the problem.

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Bryan Call
 Fix For: sometime


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2013-12-16 Thread Bryan Call (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13849800#comment-13849800
 ] 

Bryan Call commented on TS-2344:


It sounds like you are getting a request without Host: header and it is trying 
to remap it.  What does your remap.config look like?

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
Assignee: Bryan Call
 Fix For: sometime


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2013-12-05 Thread Leif Hedstrom (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840906#comment-13840906
 ] 

Leif Hedstrom commented on TS-2344:
---

[~bcall] Bryan, is this a Yahoo issue? Would yoiu mind taking a look at this ? 
It's not clear to me what the issue is, or if it it is an issue :).

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie
 Fix For: sometime


 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

2013-11-13 Thread Eddie (JIRA)


[ 
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821374#comment-13821374
 ] 

Eddie commented on TS-2344:
---

One more thing, the 'http:///' in the log message is really misleading. I spent 
a lot of time trying to figure out who is sending this empty host request.

 404 error was logged while url redirect request was processed corrctly
 --

 Key: TS-2344
 URL: https://issues.apache.org/jira/browse/TS-2344
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Eddie

 I am seeing a lot of entries in the error log for my url redirect request. 
 The request was processed correctly and I could see the expected response in 
 log as below:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed in the error log too, which 
 generates a  lot of error logs (log rotation configured) and filling up disk 
 space pretty fast.
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in 
 the error log for my url redirect request. The request was processed correctly
 I could see the expected response in log as well:
   2013-11-08 18:23:37 IP  301 FIN http://yahoo.com 
 http://www.yahoo.com/
 But log messages like following were printed too:
   20131108.18h23m37s RESPONSE: sent IP status 404 (Not Found on 
 Accelerator) for 'http:///'
   20131108.18h23m37s RESPONSE: sent IP status 301 (Redirect) 
 for 'http:///'
 I watched my tcpdump log and did not see that the 404 error was sent out at 
 all. I am using ATS/3.2.4 and following
 is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG proxy.config.log.extended2_log_name STRING extended2
 CONFIG proxy.config.log.extended2_log_header STRING NULL
 CONFIG proxy.config.log.separate_icp_logs INT 0
 CONFIG proxy.config.log.separate_host_logs INT 0
 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and 
 following is the log configuration.
 CONFIG proxy.config.log.logging_enabled INT 3
 CONFIG proxy.config.log.max_secs_per_buffer INT 1
 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000
 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25
 CONFIG proxy.config.log.max_space_mb_headroom INT 1000
 CONFIG proxy.config.log.hostname STRING localhost
 CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver
 CONFIG proxy.config.log.logfile_perm STRING rw-r--r--
 CONFIG proxy.config.log.custom_logs_enabled INT 1
 CONFIG proxy.config.log.squid_log_enabled INT 0
 CONFIG proxy.config.log.squid_log_is_ascii INT 0
 CONFIG proxy.config.log.squid_log_name STRING squid
 CONFIG proxy.config.log.squid_log_header STRING NULL
 CONFIG proxy.config.log.common_log_enabled INT 0
 CONFIG proxy.config.log.common_log_is_ascii INT 1
 CONFIG proxy.config.log.common_log_name STRING common
 CONFIG proxy.config.log.common_log_header STRING NULL
 CONFIG proxy.config.log.extended_log_enabled INT 0
 CONFIG proxy.config.log.extended_log_is_ascii INT 0
 CONFIG proxy.config.log.extended_log_name STRING extended
 CONFIG proxy.config.log.extended_log_header STRING NULL
 CONFIG proxy.config.log.extended2_log_enabled INT 0
 CONFIG proxy.config.log.extended2_log_is_ascii INT 1
 CONFIG

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly

26 matches

Site Navigation

Mail list logo

Footer information