[jira] [Commented] (TS-2564) Segmentation fault in 4.2.0-rc0
[
https://issues.apache.org/jira/browse/TS-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901356#comment-13901356
]
Igor Galić commented on TS-2564:
is this a regression since 4.1.x?
> Segmentation fault in 4.2.0-rc0
> ---
>
> Key: TS-2564
> URL: https://issues.apache.org/jira/browse/TS-2564
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
>Reporter: Bryan Call
>Assignee: Bryan Call
>Priority: Blocker
> Fix For: 4.2.0
>
>
> Segmentation fault in mime_hdr_set_accelerators_and_presence_bits() in
> 4.2.0-rc0:
> {code}
> (gdb) bt
> #0 mime_hdr_set_accelerators_and_presence_bits (mh=0x2acd02e108c8,
> field=, detach_all_dups=false) at MIME.cc:469
> #1 mime_hdr_field_detach (mh=0x2acd02e108c8, field=,
> detach_all_dups=false) at MIME.cc:1538
> #2 0x005c322c in mime_hdr_field_delete (heap=0x2acd02e10810,
> mh=0x2acd02e108c8, field=0x2acd02e10ab8, delete_all_dups= out>) at MIME.cc:1586
> #3 0x0053cb5b in field_delete (cached_header=0x2acde002fa40,
> response_header=0x2accc168b1d8) at ../../proxy/hdrs/MIME.h:1107
> #4 field_delete (cached_header=0x2acde002fa40,
> response_header=0x2accc168b1d8) at ../../proxy/hdrs/MIME.h:1115
> #5 HttpTransact::merge_response_header_with_cached_header
> (cached_header=0x2acde002fa40, response_header=0x2accc168b1d8) at
> HttpTransact.cc:4914
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (TS-2169) SSL statistics
[ https://issues.apache.org/jira/browse/TS-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Barber updated TS-2169: --- Attachment: TS-2169.patch Patch attached. (wish I could have done a pull request, but I messed up my master) I have been running a 4.0.2 version of ats in (Yahoo!) production with this patch with no issues. Added the following stats: proxy.process.https.incoming_requests Total number of inbound https requests. proxy.process.https.outgoing_requests Total number of outbound https requests. proxy.process.https.current_client_connections Current number of https connected clients. proxy.process.https.total_client_connections Total number of inbound https connections. proxy.process.https.current_server_connections Current number of https connected origins. proxy.process.https.total_server_connections Total number of outbound https connections. proxy.node.https.user_agent_total_request_bytes Total number of bytes received from https connected clients. proxy.process.https.user_agent_request_document_total_size Total size of body data received from https connected clients. proxy.process.https.user_agent_request_header_total_size Total size of request headers received from https connected clients. proxy.node.https.user_agent_total_response_bytes Total number of bytes sent to https connected clients. proxy.process.https.user_agent_response_document_total_size Total size of response body data sent to https connected clients. proxy.process.https.user_agent_response_header_total_size Total size of response headers sent to https connected clients. proxy.node.https.origin_server_total_request_bytes Total number of bytes sent to https connected origins. proxy.process.https.origin_server_request_document_total_size Total size of request body data sent to https connected origins. proxy.process.https.origin_server_request_header_total_size Total size of request headers sent to https connected origins. proxy.node.https.origin_server_total_response_bytes Total number of bytes received from https connected origins. proxy.process.https.origin_server_response_document_total_size Total size of response body data from https connected origins. proxy.process.https.origin_server_response_header_total_size Total size of header data from https connected origins. proxy.node.https.user_agent_total_bytes Total bytes transferred to/from https connected clients. proxy.node.https.origin_server_total_bytes Total bytes transferred to/from https connected origins. proxy.process.ssl.user_agent_other_errors Total number of *other* ssl client connection errors (counts ssl errors that are not captured in other user agent stats below) proxy.process.ssl.user_agent_expired_cert Total number of ssl client connection failures where the cert was expired. proxy.process.ssl.user_agent_revoked_cert Total number of ssl client connection failures where the cert was revoked. proxy.process.ssl.user_agent_unknown_cert Total number of ssl client connection failures related to the cert, but specific error was unknown. proxy.process.ssl.user_agent_cert_verify_failed Total number of ssl client connection failures where cert verification failed. proxy.process.ssl.user_agent_bad_cert Total number of ssl client connection failures where the cert is bad. proxy.process.ssl.user_agent_decryption_failed Total number of ssl client connection decryption failures (during negotiation). proxy.process.ssl.user_agent_wrong_version Total number of ssl client connections that provided an invalid protocol version. proxy.process.ssl.user_agent_unknown_ca Total number of ssl client connection that failed due to unknown ca. proxy.process.ssl.origin_server_other_errors Total number of *other* ssl origin server connection errors (counts ssl errors that are not captured in other origin server stats below). proxy.process.ssl.origin_server_expired_cert Total number of ssl origin server connection failures where the cert was expired. proxy.process.ssl.origin_server_revoked_cert Total number of ssl origin server connection failures where the cert was revoked. proxy.process.ssl.origin_server_unknown_cert Total number of ssl origin server connection failures related to the cert where specific error was unknown. proxy.process.ssl.origin_server_cert_verify_failed Total number of ssl origin server connection failures where cert verification failed. proxy.process.ssl.origin_server_bad_cert Total number of ssl origin server connection failures where the cert is bad. proxy.process.ssl.origin_server_decryption_failed Total number of ssl origin server connection decryption failures (during negotiation). proxy.process.ssl.origin_server_wrong_version Total number of ssl origin server connections that provided an invalid protocol version. proxy.process.ssl.origin_server_unknown_ca
[jira] [Commented] (TS-2569) ssl options are ignored if ssl_multicert.config does not contain an entry with dest_ip=*
[ https://issues.apache.org/jira/browse/TS-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901729#comment-13901729 ] Ron Barber commented on TS-2569: Fyi, I have been running a couple of servers with a 4.0.2 version of ats in (Yahoo!) production with this patch with no issues. > ssl options are ignored if ssl_multicert.config does not contain an entry > with dest_ip=* > - > > Key: TS-2569 > URL: https://issues.apache.org/jira/browse/TS-2569 > Project: Traffic Server > Issue Type: Bug > Components: SSL >Reporter: Ron Barber > Labels: Review > Fix For: 5.0.0 > > Attachments: TS-2569.patch > > > We discovered that the proxy.config.ssl.server.honor_cipher_order=1 setting > was not working correctly. After investigating it was determined that if you > do not have a dest_ip=* in the ssl_multicert.config file then the server > cipher order setting will not be honored. > ssl_multicert.config > dest_ip=192.168.214.131 ssl_cert_name=cert.pem > records.config > CONFIG proxy.config.ssl.server.cipher_suite STRING > RC4-SHA:AES128-SHA:DES-CBC3-SHA:AES256-SHA:ALL:!NULL > CONFIG proxy.config.ssl.server.honor_cipher_order INT 1 > Result (client selection is honored): > % echo | openssl s_client -connect 192.168.214.131:443 -cipher > 'AES128-SHA:RC4-SHA' 2>&1 | grep 'Cipher is' > New, TLSv1/SSLv3, Cipher is AES128-SHA > % echo | openssl s_client -connect 192.168.214.131:443 -cipher > 'RC4-SHA:AES128-SHA' 2>&1 | grep 'Cipher is' > New, TLSv1/SSLv3, Cipher is RC4-SHA -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (TS-2362) Backwards cache compatibility for 4.X (read 3.2)
[ https://issues.apache.org/jira/browse/TS-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan M. Carroll updated TS-2362: Attachment: ts-2362.diff > Backwards cache compatibility for 4.X (read 3.2) > > > Key: TS-2362 > URL: https://issues.apache.org/jira/browse/TS-2362 > Project: Traffic Server > Issue Type: Improvement > Components: Cache >Reporter: Alan M. Carroll >Assignee: Alan M. Carroll > Fix For: 5.0.0 > > Attachments: ts-2362.diff > > > Enable the 4.X series to be able to read 3.2 caches. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (TS-2362) Backwards cache compatibility for 4.X (read 3.2)
[ https://issues.apache.org/jira/browse/TS-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901881#comment-13901881 ] Alan M. Carroll commented on TS-2362: - I have an alpha version of the patch. It needs some more work but it is a big enough patch and far enough along to need some feedback. In addition to backwards compatibility, it also does some clean up with the URL hashing logic, due to TS-1925. > Backwards cache compatibility for 4.X (read 3.2) > > > Key: TS-2362 > URL: https://issues.apache.org/jira/browse/TS-2362 > Project: Traffic Server > Issue Type: Improvement > Components: Cache >Reporter: Alan M. Carroll >Assignee: Alan M. Carroll > Fix For: 5.0.0 > > Attachments: ts-2362.diff > > > Enable the 4.X series to be able to read 3.2 caches. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (TS-2564) Segmentation fault in 4.2.0-rc0
[
https://issues.apache.org/jira/browse/TS-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901909#comment-13901909
]
Bryan Call commented on TS-2564:
We are testing 2 version right now:
{code}
commit 2b0351f43d64a2fd69c7f95d81df4a163826999d
Author: Igor Gali<87>
Date: Thu Nov 7 00:49:24 2013 +0100
jenkins config: Prepare for 4.1.x release cycle
commit 2a979548dbf17dea5fbeb43e79116b4c3dcf4a6e
Author: Ron Barber
Date: Mon Dec 16 14:56:32 2013 -0800
TS-2355: ATS 4.0.x crashes when using OpenSSL 1.0.1e
{code}
git bisect log:
{code}
$ git bisect log
git bisect start
# good: [de710cb9b33375abbb4dfae5ac078bc8daefb540] reliably recreate the same
tar-ball from the same content
git bisect good de710cb9b33375abbb4dfae5ac078bc8daefb540
# bad: [f0f9cb9c3521873df900ece090b890d789d50594] Update CHANGES for TS-2550
git bisect bad f0f9cb9c3521873df900ece090b890d789d50594
# good: [2b0351f43d64a2fd69c7f95d81df4a163826999d] jenkins config: Prepare for
4.1.x release cycle
git bisect good 2b0351f43d64a2fd69c7f95d81df4a163826999d
{code}
> Segmentation fault in 4.2.0-rc0
> ---
>
> Key: TS-2564
> URL: https://issues.apache.org/jira/browse/TS-2564
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
>Reporter: Bryan Call
>Assignee: Bryan Call
>Priority: Blocker
> Fix For: 4.2.0
>
>
> Segmentation fault in mime_hdr_set_accelerators_and_presence_bits() in
> 4.2.0-rc0:
> {code}
> (gdb) bt
> #0 mime_hdr_set_accelerators_and_presence_bits (mh=0x2acd02e108c8,
> field=, detach_all_dups=false) at MIME.cc:469
> #1 mime_hdr_field_detach (mh=0x2acd02e108c8, field=,
> detach_all_dups=false) at MIME.cc:1538
> #2 0x005c322c in mime_hdr_field_delete (heap=0x2acd02e10810,
> mh=0x2acd02e108c8, field=0x2acd02e10ab8, delete_all_dups= out>) at MIME.cc:1586
> #3 0x0053cb5b in field_delete (cached_header=0x2acde002fa40,
> response_header=0x2accc168b1d8) at ../../proxy/hdrs/MIME.h:1107
> #4 field_delete (cached_header=0x2acde002fa40,
> response_header=0x2accc168b1d8) at ../../proxy/hdrs/MIME.h:1115
> #5 HttpTransact::merge_response_header_with_cached_header
> (cached_header=0x2acde002fa40, response_header=0x2accc168b1d8) at
> HttpTransact.cc:4914
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (TS-1893) Make ATS use keep-alive connections per origin address
[ https://issues.apache.org/jira/browse/TS-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13902074#comment-13902074 ] ASF subversion and git services commented on TS-1893: - Commit 0d8bfb404df781637da317af68487d8b10671152 in trafficserver's branch refs/heads/master from [~amc] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=0d8bfb4 ] TS-1893 Add configuration options for server session matching. > Make ATS use keep-alive connections per origin address > -- > > Key: TS-1893 > URL: https://issues.apache.org/jira/browse/TS-1893 > Project: Traffic Server > Issue Type: Improvement > Components: HTTP, Network, Performance >Reporter: Tomasz Kuzemko >Assignee: Alan M. Carroll > Fix For: 5.0.0 > > Attachments: TS-1893-PoC.diff > > > In current implementation Traffic Server uses a two level hash for keep-alive > connections: server ip -> hostname -> keep-alive session. > The reasoning behind this was that some old http servers could not handle the > request properly for different virtual hosts on the same keep-alive session. > Recent web servers should all handle this situation correctly. > The improvement would be to make a single level hash to keep just the server > ip. Shared hosting configurations using ATS as a reverse-proxy could benefit > the most from this improvement. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (TS-2362) Backwards cache compatibility for 4.X (read 3.2)
[ https://issues.apache.org/jira/browse/TS-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Peach updated TS-2362: Labels: Review (was: ) > Backwards cache compatibility for 4.X (read 3.2) > > > Key: TS-2362 > URL: https://issues.apache.org/jira/browse/TS-2362 > Project: Traffic Server > Issue Type: Improvement > Components: Cache >Reporter: Alan M. Carroll >Assignee: Alan M. Carroll > Labels: Review > Fix For: 5.0.0 > > Attachments: ts-2362.diff > > > Enable the 4.X series to be able to read 3.2 caches. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (TS-2169) SSL statistics
[ https://issues.apache.org/jira/browse/TS-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Peach updated TS-2169: Labels: Review (was: ) > SSL statistics > -- > > Key: TS-2169 > URL: https://issues.apache.org/jira/browse/TS-2169 > Project: Traffic Server > Issue Type: Improvement > Components: SSL, Stats >Reporter: David Carlin > Labels: Review > Fix For: 5.1.0 > > Attachments: TS-2169.patch > > > It would be swell if there were some traffic_line SSL statistic variables. > For instance, number of SSL connections and SSL bytes. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (TS-2571) Describe directory structure in docs
Miles Libbey created TS-2571: Summary: Describe directory structure in docs Key: TS-2571 URL: https://issues.apache.org/jira/browse/TS-2571 Project: Traffic Server Issue Type: Improvement Components: Documentation Reporter: Miles Libbey It doesn't appear that we describe the directory structure for users in the documentation -- eg, where do I find config files? Where do I find tools? While we can't say definitively the absolute path, we could describe the defaults. For instance, in admin/getting-started.en.html we could tell users where to look for configurations files and tools. Similarly, in each of the files in doc/reference/configuration, seems like there should be a sentence about where to find the file. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (TS-1606) Log buffers are not flushed periodically when TS is launched with NO_REMOTE_MANAGEMENT flag
[
https://issues.apache.org/jira/browse/TS-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-1606:
--
Backport to Version: (was: 4.1.3)
> Log buffers are not flushed periodically when TS is launched with
> NO_REMOTE_MANAGEMENT flag
> ---
>
> Key: TS-1606
> URL: https://issues.apache.org/jira/browse/TS-1606
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
>Affects Versions: 3.3.0, 3.2.0
>Reporter: Yakov Markovitch
>Assignee: Uri Shachar
> Fix For: 4.2.0
>
> Attachments: trafficserver-periodic-tasks.patch
>
>
> When TS binary is launched with NO_REMOTE_MANAGEMENT flag (e.g., when
> launched not as a daemon but directly - this is extremely convenient for
> debugging), the PeriodicWakeup event is not scheduled.
> As a result, Log::flush_thread_main() does not wake up periodically, but only
> on log buffer overflow. Coupled with a horribly wrong activation check in
> Log::flush_thread_main():
> {code}
> if (now > last_time) {
> if ((now % PERIODIC_TASKS_INTERVAL) == 0) {
> // We run only when waken up at the moment which is exact
> // multiple of PERIODIC_TASKS_INTERVAL!
> {code}
> this leads to that probability of any log output is low.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (TS-2560) regex_remap lowercase substitutions is not being initialized in the construtor
[ https://issues.apache.org/jira/browse/TS-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2560: -- Assignee: Bryan Call > regex_remap lowercase substitutions is not being initialized in the construtor > -- > > Key: TS-2560 > URL: https://issues.apache.org/jira/browse/TS-2560 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: Bryan Call >Assignee: Bryan Call > Fix For: 5.0.0 > > > Report of this being turned on sometimes and having to set the option off in > the config to make sure it is set to false. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (TS-2571) Describe directory structure in docs
[ https://issues.apache.org/jira/browse/TS-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2571: -- Fix Version/s: Docs > Describe directory structure in docs > > > Key: TS-2571 > URL: https://issues.apache.org/jira/browse/TS-2571 > Project: Traffic Server > Issue Type: Improvement > Components: Documentation >Reporter: Miles Libbey > Fix For: Docs > > > It doesn't appear that we describe the directory structure for users in the > documentation -- eg, where do I find config files? Where do I find tools? > While we can't say definitively the absolute path, we could describe the > defaults. > For instance, in admin/getting-started.en.html we could tell users where to > look for configurations files and tools. Similarly, in each of the files in > doc/reference/configuration, seems like there should be a sentence about > where to find the file. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (TS-2560) regex_remap lowercase substitutions is not being initialized in the construtor
[ https://issues.apache.org/jira/browse/TS-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2560: -- Fix Version/s: 5.0.0 > regex_remap lowercase substitutions is not being initialized in the construtor > -- > > Key: TS-2560 > URL: https://issues.apache.org/jira/browse/TS-2560 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: Bryan Call >Assignee: Bryan Call > Fix For: 5.0.0 > > > Report of this being turned on sometimes and having to set the option off in > the config to make sure it is set to false. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (TS-2570) Reduce/Remove fast path malloc/free's in remap_stats
[ https://issues.apache.org/jira/browse/TS-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2570: -- Fix Version/s: 5.0.0 > Reduce/Remove fast path malloc/free's in remap_stats > > > Key: TS-2570 > URL: https://issues.apache.org/jira/browse/TS-2570 > Project: Traffic Server > Issue Type: Improvement > Components: Plugins >Reporter: Phil Sorber >Assignee: Phil Sorber > Fix For: 5.0.0 > > > The remap_stats plugin was recently introduced into experimental. It has a > lot of memory allocation in the fast path that needs to be removed. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (TS-2560) regex_remap lowercase substitutions is not being initialized in the construtor
[ https://issues.apache.org/jira/browse/TS-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1390#comment-1390 ] Leif Hedstrom commented on TS-2560: --- [~bcall] This is done, right ? > regex_remap lowercase substitutions is not being initialized in the construtor > -- > > Key: TS-2560 > URL: https://issues.apache.org/jira/browse/TS-2560 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: Bryan Call >Assignee: Bryan Call > Fix For: 5.0.0 > > > Report of this being turned on sometimes and having to set the option off in > the config to make sure it is set to false. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (TS-2566) ALPN: HTTP client support
[ https://issues.apache.org/jira/browse/TS-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2566: -- Fix Version/s: sometime > ALPN: HTTP client support > - > > Key: TS-2566 > URL: https://issues.apache.org/jira/browse/TS-2566 > Project: Traffic Server > Issue Type: New Feature > Components: Core, HTTP, SSL >Reporter: James Peach > Fix For: sometime > > > The HTTP client should use ALPN when opening TLS sessions with origin servers. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (TS-2555) Move existing lua plugin to plugins/deprecated and rename ts_lua to lua
[ https://issues.apache.org/jira/browse/TS-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2555: -- Fix Version/s: 5.0.0 > Move existing lua plugin to plugins/deprecated and rename ts_lua to lua > --- > > Key: TS-2555 > URL: https://issues.apache.org/jira/browse/TS-2555 > Project: Traffic Server > Issue Type: Task > Components: Plugins >Reporter: Kit Chan >Assignee: Kit Chan > Fix For: 5.0.0 > > > As suggested by Igor Galic in TS-2335, "to avoid namespace pollution, we > could move move the old Lua plugin to plugins/deprecated, and name this one > lua again from the start. From what I gather, the consensus on the mailing > list was to replace the old plugin with this one. > Given that the old plugin was experimental, and we've decided that all bets > regarding compatibility and stability are off in experimental, I'm fairly > certain we can just do that. I'd move it, for easy reference into > plugins/deprecated, remove it from the build, and once the new plugin has > absorbed all of its features, remove it all together." -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (TS-2568) body_factory's access#redirect_url uses questionable English
[
https://issues.apache.org/jira/browse/TS-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2568:
--
Fix Version/s: 5.0.0
> body_factory's access#redirect_url uses questionable English
>
>
> Key: TS-2568
> URL: https://issues.apache.org/jira/browse/TS-2568
> Project: Traffic Server
> Issue Type: Bug
>Reporter: Igor Galić
> Fix For: 5.0.0
>
>
> from {{{proxy/config/body_factory/default/access#redirect_url}}
> {code}
> Please wait while u r redirected to another page.
> {code}
> I think we can do better than that.
> Btw, I haven't reviewed all pages yet, perhaps there are other candidates.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Assigned] (TS-2568) body_factory's access#redirect_url uses questionable English
[
https://issues.apache.org/jira/browse/TS-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom reassigned TS-2568:
-
Assignee: Leif Hedstrom
> body_factory's access#redirect_url uses questionable English
>
>
> Key: TS-2568
> URL: https://issues.apache.org/jira/browse/TS-2568
> Project: Traffic Server
> Issue Type: Bug
>Reporter: Igor Galić
>Assignee: Leif Hedstrom
> Fix For: 5.0.0
>
>
> from {{{proxy/config/body_factory/default/access#redirect_url}}
> {code}
> Please wait while u r redirected to another page.
> {code}
> I think we can do better than that.
> Btw, I haven't reviewed all pages yet, perhaps there are other candidates.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (TS-2531) The default remap rule doesn't match a forward proxy request
[ https://issues.apache.org/jira/browse/TS-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2531: -- Assignee: Bryan Call > The default remap rule doesn't match a forward proxy request > > > Key: TS-2531 > URL: https://issues.apache.org/jira/browse/TS-2531 > Project: Traffic Server > Issue Type: Bug > Components: HTTP >Reporter: Bryan Call >Assignee: Bryan Call > Fix For: 5.0.0 > > Attachments: 0001-fix-bug-TS_2531.patch > > > when doing a forward proxy request it won't math the default rule, but will > match other rules that specify the hostname. > Example request: > GET http://foo.yahoo.com HTTP/1.1 > Host: foo.yahoo.com > remap.config: > map / http://www.yahoo.com > Response: > HTTP/1.1 404 Not Found > ... > > However, this works: > remap.config: > map http://foo.yahoo.com http://www.yahoo.com -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (TS-2531) The default remap rule doesn't match a forward proxy request
[ https://issues.apache.org/jira/browse/TS-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2531: -- Fix Version/s: 5.0.0 > The default remap rule doesn't match a forward proxy request > > > Key: TS-2531 > URL: https://issues.apache.org/jira/browse/TS-2531 > Project: Traffic Server > Issue Type: Bug > Components: HTTP >Reporter: Bryan Call >Assignee: Bryan Call > Fix For: 5.0.0 > > Attachments: 0001-fix-bug-TS_2531.patch > > > when doing a forward proxy request it won't math the default rule, but will > match other rules that specify the hostname. > Example request: > GET http://foo.yahoo.com HTTP/1.1 > Host: foo.yahoo.com > remap.config: > map / http://www.yahoo.com > Response: > HTTP/1.1 404 Not Found > ... > > However, this works: > remap.config: > map http://foo.yahoo.com http://www.yahoo.com -- This message was sent by Atlassian JIRA (v6.1.5#6160)
