[jira] [Comment Edited] (TS-2344) 404 error was logged while url redirect request was processed corrctly
[ https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1400#comment-1400 ] Bryan Call edited comment on TS-2344 at 5/23/14 10:16 PM: -- Looking at the latest patch, I 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. was (Author: bcall): 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
[jira] [Comment Edited] (TS-2344) 404 error was logged while url redirect request was processed corrctly
[
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14000683#comment-14000683
]
Ethan Lai edited comment on TS-2344 at 5/20/14 2:15 PM:
[~zwoop] This 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}
Current redirect_temporary response body (Please notice the empty Location):
{code}
HTTP/1.1 307 Redirect
Date: Sat, 17 May 2014 05:55:21 GMT
Server: ATS
Cache-Control: no-store
Content-Type: text/html; charset=utf-8
Content-Language: en
Connection: close
Location: https://www.example.com/
Content-Length: 283
HTML
HEAD
TITLEDocument Has Moved/TITLE
/HEAD
BODY BGCOLOR=white FGCOLOR=black
H1Document Has Moved/H1
HR
FONT FACE=Helvetica,ArialB
Description: The document you requested has moved to a new location. The new
location is -.
/B/FONT
HR
/BODY
{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. :)
was (Author: yzlai):
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}
Current redirect_temporary response body (Please notice the empty Location):
{code}
HTTP/1.1 307 Redirect
Date: Sat, 17 May 2014 05:55:21 GMT
Server: ATS
Cache-Control: no-store
Content-Type: text/html; charset=utf-8
Content-Language: en
Connection: close
Location: https://www.example.com/
Content-Length: 283
HTML
HEAD
TITLEDocument Has Moved/TITLE
/HEAD
BODY BGCOLOR=white FGCOLOR=black
H1Document Has Moved/H1
HR
FONT FACE=Helvetica,ArialB
Description: The document you requested has moved to a new location. The new
location is -.
/B/FONT
HR
/BODY
{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: 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.
[jira] [Comment Edited] (TS-2344) 404 error was logged while url redirect request was processed corrctly
[
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14000683#comment-14000683
]
Ethan Lai edited comment on TS-2344 at 5/17/14 5:56 AM:
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}
Current redirect_temporary response body (Please notice the empty Location):
{code}
HTTP/1.1 307 Redirect
Date: Sat, 17 May 2014 05:55:21 GMT
Server: ATS
Cache-Control: no-store
Content-Type: text/html; charset=utf-8
Content-Language: en
Connection: close
Location: https://www.example.com/
Content-Length: 283
HTML
HEAD
TITLEDocument Has Moved/TITLE
/HEAD
BODY BGCOLOR=white FGCOLOR=black
H1Document Has Moved/H1
HR
FONT FACE=Helvetica,ArialB
Description: The document you requested has moved to a new location. The new
location is -.
/B/FONT
HR
/BODY
{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. :)
was (Author: yzlai):
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
[jira] [Comment Edited] (TS-2344) 404 error was logged while url redirect request was processed corrctly
[
https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998898#comment-13998898
]
Leif Hedstrom edited comment on TS-2344 at 5/15/14 4:54 PM:
Ok, so reading this last set of diffs, why is this necessary:
{code}
-remap_redirect = redirect_url.string_get_ref(remap_redirect_len);
+s-remap_redirect = redirect_url.string_get(NULL, remap_redirect_len);
+redirect_url.destroy();
{code}
This seems like a significant degradation in performance.
was (Author: zwoop):
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
[jira] [Comment Edited] (TS-2344) 404 error was logged while url redirect request was processed corrctly
[ https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13999459#comment-13999459 ] Ethan Lai edited comment on TS-2344 at 5/16/14 12:36 AM: - [~zwoop] 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. Sorry for my so old branch, you can use this patch, https://github.com/apache/trafficserver/pull/86.patch, to review :) was (Author: yzlai): [~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
[jira] [Comment Edited] (TS-2344) 404 error was logged while url redirect request was processed corrctly
[ https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997108#comment-13997108 ] Ethan Lai edited comment on TS-2344 at 5/14/14 12:36 AM: - [~zwoop] I've close previous pull request and create a new one with this patch, which remove handleIfRedirect() in done section. I'm done with this ticket, please kindly review it. was (Author: yzlai): [~zwoop] I've close previous pull request and create a new one with this patch, which remove handleIfRedirect() in done section. Please kindly review 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: 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
[jira] [Comment Edited] (TS-2344) 404 error was logged while url redirect request was processed corrctly
[ https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996460#comment-13996460 ] Leif Hedstrom edited comment on TS-2344 at 5/13/14 2:55 PM: [~yzlai] ping on this patch? Should we commit it, or are you working on this still? was (Author: zwoop): [~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
[jira] [Comment Edited] (TS-2344) 404 error was logged while url redirect request was processed corrctly
[ https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13961581#comment-13961581 ] Ethan Lai edited comment on TS-2344 at 4/7/14 12:13 AM: [~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\.\-]+)\.example.com/ https://$1.example.com/ Since remap rules are first matched, would it be better to stop redirect match after a success map? was (Author: yzlai): [~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
[jira] [Comment Edited] (TS-2344) 404 error was logged while url redirect request was processed corrctly
[ https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960911#comment-13960911 ] Leif Hedstrom edited comment on TS-2344 at 4/5/14 2:11 AM: --- [~eddie] The patch does indeed solve the problem with the additional log line. However, I really wonder if we should eliminate all error logs for 3xx responses? They are of course not errors, so I don't know why they go in there. If you have the time, and can provide a patch with that, that'd be great. If not, we should file a separate bug on that issue. [~yzlai] Not quite sure I follow, you have a different patch in mind ? Or something in addition to Eddie's? Thanks! was (Author: zwoop): [~eddie] The patch does indeed solve the problem with the additional log line. However, I really wonder if we should eliminate all error logs for 3xx responses? They are of course not errors, so I don't know why they go in there. If you have the time, and can provide a patch with that, that'd be great. If not, we should file a separate bug on that issue. [~yzlai] Not quite sure I follow, you have a different patch in mind ? 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
[jira] [Comment Edited] (TS-2344) 404 error was logged while url redirect request was processed corrctly
[ https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917889#comment-13917889 ] Bryan Call edited comment on TS-2344 at 3/4/14 10:37 AM: - [~yzlai] 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... was (Author: bcall): 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
[jira] [Comment Edited] (TS-2344) 404 error was logged while url redirect request was processed corrctly
[ https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850521#comment-13850521 ] Eddie edited comment on TS-2344 at 12/17/13 2:54 PM: - I am not working for Yahoo. You should not be able to connect to my server directly because of FW. 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 was (Author: eddie): 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
[jira] [Comment Edited] (TS-2344) 404 error was logged while url redirect request was processed corrctly
[ https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850521#comment-13850521 ] Eddie edited comment on TS-2344 at 12/17/13 2:56 PM: - I am not working for Yahoo. You should not be able to connect to my server directly because of FW. 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 Could you please let me know when you are available? was (Author: eddie): I am not working for Yahoo. You should not be able to connect to my server directly because of FW. 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
[jira] [Comment Edited] (TS-2344) 404 error was logged while url redirect request was processed corrctly
[ https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850521#comment-13850521 ] Eddie edited comment on TS-2344 at 12/17/13 3:06 PM: - I am not working for Yahoo. You should not be able to connect to my server directly because of FW. 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 Could you please let me know when you are available? I am on messenger with ID: zteddie. Please ping me if you can. was (Author: eddie): I am not working for Yahoo. You should not be able to connect to my server directly because of FW. 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 Could you please let me know when you are available? 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
