[jira] [Commented] (TS-1366) cquc does not work as documented: Logging the remapped URL
[
https://issues.apache.org/jira/browse/TS-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13635049#comment-13635049
]
ASF subversion and git services commented on TS-1366:
-
Commit 85ef72268a612c5230285cfb4b6dd48a64fadc8a in branch
refs/heads/sphinx-docs from [~amc]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=85ef722 ]
TS-1366: Update logging formats for remapped vs. pristine.
cquc does not work as documented: Logging the remapped URL
--
Key: TS-1366
URL: https://issues.apache.org/jira/browse/TS-1366
Project: Traffic Server
Issue Type: Bug
Components: Documentation
Reporter: Igor Galić
Assignee: Alan M. Carroll
Fix For: Doc 3.4
Attachments: ts-1366.diff
From the documentation
(http://trafficserver.apache.org/docs/trunk/admin/working-log-files/log-formats#SquidFormat)
:
cquc
The client request canonical URL; blanks and other characters that might
not be parsed by log analysis tools are replaced by escape sequences. The
escape sequence is a percentage sign followed by the ASCII code number of the
replaced character in hex.
But in fact it logs the remapped URL.
This may or may not be related to the {{records.config}} setting:
{noformat}
CONFIG proxy.config.url_remap.pristine_host_hdr INT 1
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1366) cquc does not work as documented: Logging the remapped URL
[
https://issues.apache.org/jira/browse/TS-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616358#comment-13616358
]
ASF subversion and git services commented on TS-1366:
-
Commit 1462158 from amc
[ https://svn.apache.org/r1462158 ]
TS-1366: Update for logging formats, remapped vs. pristine
cquc does not work as documented: Logging the remapped URL
--
Key: TS-1366
URL: https://issues.apache.org/jira/browse/TS-1366
Project: Traffic Server
Issue Type: Bug
Components: Documentation
Reporter: Igor Galić
Assignee: Alan M. Carroll
Fix For: Doc 3.4
Attachments: ts-1366.diff
From the documentation
(http://trafficserver.apache.org/docs/trunk/admin/working-log-files/log-formats#SquidFormat)
:
cquc
The client request canonical URL; blanks and other characters that might
not be parsed by log analysis tools are replaced by escape sequences. The
escape sequence is a percentage sign followed by the ASCII code number of the
replaced character in hex.
But in fact it logs the remapped URL.
This may or may not be related to the {{records.config}} setting:
{noformat}
CONFIG proxy.config.url_remap.pristine_host_hdr INT 1
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1366) cquc does not work as documented: Logging the remapped URL
[
https://issues.apache.org/jira/browse/TS-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13615691#comment-13615691
]
Leif Hedstrom commented on TS-1366:
---
I'd say just commit it :)
cquc does not work as documented: Logging the remapped URL
--
Key: TS-1366
URL: https://issues.apache.org/jira/browse/TS-1366
Project: Traffic Server
Issue Type: Bug
Components: Documentation
Reporter: Igor Galić
Assignee: Alan M. Carroll
Fix For: Doc 3.4
Attachments: ts-1366.diff
From the documentation
(http://trafficserver.apache.org/docs/trunk/admin/working-log-files/log-formats#SquidFormat)
:
cquc
The client request canonical URL; blanks and other characters that might
not be parsed by log analysis tools are replaced by escape sequences. The
escape sequence is a percentage sign followed by the ASCII code number of the
replaced character in hex.
But in fact it logs the remapped URL.
This may or may not be related to the {{records.config}} setting:
{noformat}
CONFIG proxy.config.url_remap.pristine_host_hdr INT 1
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1366) cquc does not work as documented: Logging the remapped URL
[
https://issues.apache.org/jira/browse/TS-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614087#comment-13614087
]
Alan M. Carroll commented on TS-1366:
-
Looking at the code, I don't see how this is expected to work. I can find the
logic to do it, but not any place where it is called. I also don't see how cqu
works any differently. At this point it would be easier to add a couple of
extra fields to do the pristine versions.
cquc does not work as documented: Logging the remapped URL
--
Key: TS-1366
URL: https://issues.apache.org/jira/browse/TS-1366
Project: Traffic Server
Issue Type: Bug
Components: Logging
Reporter: Igor Galić
Assignee: Alan M. Carroll
Fix For: 3.3.3
From the documentation
(http://trafficserver.apache.org/docs/trunk/admin/working-log-files/log-formats#SquidFormat)
:
cquc
The client request canonical URL; blanks and other characters that might
not be parsed by log analysis tools are replaced by escape sequences. The
escape sequence is a percentage sign followed by the ASCII code number of the
replaced character in hex.
But in fact it logs the remapped URL.
This may or may not be related to the {{records.config}} setting:
{noformat}
CONFIG proxy.config.url_remap.pristine_host_hdr INT 1
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1366) cquc does not work as documented: Logging the remapped URL
[
https://issues.apache.org/jira/browse/TS-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614105#comment-13614105
]
Zhao Yongming commented on TS-1366:
---
you want the unmaped url? use cquuc
cquc does not work as documented: Logging the remapped URL
--
Key: TS-1366
URL: https://issues.apache.org/jira/browse/TS-1366
Project: Traffic Server
Issue Type: Bug
Components: Logging
Reporter: Igor Galić
Assignee: Alan M. Carroll
Fix For: 3.3.3
From the documentation
(http://trafficserver.apache.org/docs/trunk/admin/working-log-files/log-formats#SquidFormat)
:
cquc
The client request canonical URL; blanks and other characters that might
not be parsed by log analysis tools are replaced by escape sequences. The
escape sequence is a percentage sign followed by the ASCII code number of the
replaced character in hex.
But in fact it logs the remapped URL.
This may or may not be related to the {{records.config}} setting:
{noformat}
CONFIG proxy.config.url_remap.pristine_host_hdr INT 1
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1366) cquc does not work as documented: Logging the remapped URL
[
https://issues.apache.org/jira/browse/TS-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614280#comment-13614280
]
Alan M. Carroll commented on TS-1366:
-
The code works as intended, this is a documentation issue. I will update the
docs to correctly explain the implementation. In very short summary, there are
additional codes (cquuc in this case, as noted) that are to be used for the
pristine data to be logged.
cquc does not work as documented: Logging the remapped URL
--
Key: TS-1366
URL: https://issues.apache.org/jira/browse/TS-1366
Project: Traffic Server
Issue Type: Bug
Components: Logging
Reporter: Igor Galić
Assignee: Alan M. Carroll
Fix For: 3.3.3
From the documentation
(http://trafficserver.apache.org/docs/trunk/admin/working-log-files/log-formats#SquidFormat)
:
cquc
The client request canonical URL; blanks and other characters that might
not be parsed by log analysis tools are replaced by escape sequences. The
escape sequence is a percentage sign followed by the ASCII code number of the
replaced character in hex.
But in fact it logs the remapped URL.
This may or may not be related to the {{records.config}} setting:
{noformat}
CONFIG proxy.config.url_remap.pristine_host_hdr INT 1
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1366) cquc does not work as documented: Logging the remapped URL
[
https://issues.apache.org/jira/browse/TS-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614532#comment-13614532
]
Alan M. Carroll commented on TS-1366:
-
Added patch for documentation.
cquc does not work as documented: Logging the remapped URL
--
Key: TS-1366
URL: https://issues.apache.org/jira/browse/TS-1366
Project: Traffic Server
Issue Type: Bug
Components: Logging
Reporter: Igor Galić
Assignee: Alan M. Carroll
Fix For: 3.3.3
Attachments: ts-1366.diff
From the documentation
(http://trafficserver.apache.org/docs/trunk/admin/working-log-files/log-formats#SquidFormat)
:
cquc
The client request canonical URL; blanks and other characters that might
not be parsed by log analysis tools are replaced by escape sequences. The
escape sequence is a percentage sign followed by the ASCII code number of the
replaced character in hex.
But in fact it logs the remapped URL.
This may or may not be related to the {{records.config}} setting:
{noformat}
CONFIG proxy.config.url_remap.pristine_host_hdr INT 1
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
