[jira] [Updated] (TS-1058) Intercept an HTTP client's request
[
https://issues.apache.org/jira/browse/TS-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yakov Kopel updated TS-1058:
Fix Version/s: (was: 3.3.0)
3.1.4
I attached a patch that is working
Intercept an HTTP client's request
--
Key: TS-1058
URL: https://issues.apache.org/jira/browse/TS-1058
Project: Traffic Server
Issue Type: Bug
Components: TS API
Affects Versions: 3.1.1
Reporter: Yakov Kopel
Labels: patch
Fix For: 3.1.4
Attachments: patch.diff
Original Estimate: 24h
Remaining Estimate: 24h
I want that the trafficserver will give the client the response instead of
the server.
The trafficserver offers the INKHttpTxnIntercept api to do so, but it is not
so convenience to use it.
I want to use the regular flow of the trafficserver, and its regular parsing
commands.
The trafficserver's plugins examples also aren't using the
INKHttpTxnIntercept , but they rather using the rasing error method, and
then they response the request at the response hook.
So, this is whta i did.
On the global-hook at the TS_EVENT_HTTP_READ_REQUEST_HDR i raised
TS_EVENT_HTTP_ERROR.
I also added TS_HTTP_SEND_RESPONSE_HDR_HOOK and there i returned http
response with the KEEP-ALIVE header.
The problem is that the trafficserver is closing the connection although i
added to the response the KEEP-ALIVE header.
When the Trafficserver is trying to send response to the client, it terminate
the session after it.
Although I added the KEEP-ALIVE mime field - it didn't work.
The debug dump is looking like this:
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::state_api_callback, HTTP_API_CONTINUE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::state_api_callout, HTTP_API_CONTINUE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpSM::do_redirect]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4]
adding producer 'internal msg'
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4]
adding consumer 'user agent'
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel)
tunnel_run started, p_arg is NULL
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4]
consumer_handler [user agent VC_EVENT_WRITE_COMPLETE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::tunnel_handler_ua, VC_EVENT_WRITE_COMPLETE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_cs) [4] session
closed
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_cs) [4] session
destroy
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::main_handler, HTTP_TUNNEL_EVENT_DONE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::tunnel_handler, HTTP_TUNNEL_EVENT_DONE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4] calling
plugin on hook TS_HTTP_TXN_CLOSE_HOOK at hook 0x3B97610
The Solution:
I'm adding a patch of functino that rasing the internal flag of KEEP-ALIVE,
so the trafficserver will realy believe us that we want to keep this
connection alive :)
Example for the usage of the new function:
// Tell the trafficserver to not close this connection (keep-alive)
TSHttpTxnCloseAfterResponse(txnp, 0);
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1127) Wrong assignment of incoming address
[ https://issues.apache.org/jira/browse/TS-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yakov Kopel updated TS-1127: Description: The API TSHttpTxnClientIncomingPortGet has been changed in Wed Oct 5 19:14:07 2011 (TS-926) and it returns another value. in the old version it returned the incoming port of the TS(the port which the client connected to the TS). in the new version the returned value is the sending port of the user. The different is in the line: - return sm-t_state.client_info.port; + return ink_inet_get_port(sm-t_state.client_info.addr); The assignment of those two members (port, addr) are in the HttpSM.cc file ink_inet_copy(t_state.client_info.addr, netvc-get_remote_addr()); t_state.client_info.port = netvc-get_local_port(); The old code gave the right answer from the port member, and the new one gives us wrong answer from the remote address. I attached a patch to fix this returned value. was: There is a problem in the new version of trafficserverin the function (HttpSM.cc): TSHttpTxnClientIncomingPortGet The old code: return sm-t_state.client_info.port The new code: return ink_inet_get_port(sm-t_state.client_info.addr); The assignment of those two members (port, addr) are in the HttpSM.cc file (in attach_client_session function): ink_inet_copy(t_state.client_info.addr, netvc-get_remote_addr()); t_state.client_info.port = netvc-get_local_port(); the old code gave the right answer from the port member, and the new one gives us wrong answer fron the remote addr. I thought to fix it by rewrite the code get_remote_addr = get_local_addr (as in the patch that I attached to here) But it makes bugs in other places (redirect to another address). Or maybe it will be better to rewrite the TSHttpTxnClientIncomingPortGet function to the old version. Wrong assignment of incoming address Key: TS-1127 URL: https://issues.apache.org/jira/browse/TS-1127 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 3.1.2 Reporter: Yakov Kopel Fix For: 3.1.4 Attachments: fix.patch, fix.patch Original Estimate: 1m Remaining Estimate: 1m The API TSHttpTxnClientIncomingPortGet has been changed in Wed Oct 5 19:14:07 2011 (TS-926) and it returns another value. in the old version it returned the incoming port of the TS(the port which the client connected to the TS). in the new version the returned value is the sending port of the user. The different is in the line: - return sm-t_state.client_info.port; + return ink_inet_get_port(sm-t_state.client_info.addr); The assignment of those two members (port, addr) are in the HttpSM.cc file ink_inet_copy(t_state.client_info.addr, netvc-get_remote_addr()); t_state.client_info.port = netvc-get_local_port(); The old code gave the right answer from the port member, and the new one gives us wrong answer from the remote address. I attached a patch to fix this returned value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1127) Wrong assignment of incoming address
[ https://issues.apache.org/jira/browse/TS-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yakov Kopel updated TS-1127: Attachment: fix.patch Wrong assignment of incoming address Key: TS-1127 URL: https://issues.apache.org/jira/browse/TS-1127 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 3.1.2 Reporter: Yakov Kopel Fix For: 3.1.4 Attachments: fix.patch Original Estimate: 1m Remaining Estimate: 1m In HttpSM.cc file (attach_client_session) there are two lines: ink_inet_copy(t_state.client_info.addr, netvc-get_remote_addr()); t_state.client_info.port = netvc-get_local_port(); instead of: ink_inet_copy(t_state.client_info.addr, netvc-get_local_addr()); t_state.client_info.port = netvc-get_local_port(); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1127) Wrong assignment of incoming address
[ https://issues.apache.org/jira/browse/TS-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yakov Kopel updated TS-1127: Description: There is a problem in the new version of trafficserverin the function (HttpSM.cc): TSHttpTxnClientIncomingPortGet The old code: return sm-t_state.client_info.port The new code: return ink_inet_get_port(sm-t_state.client_info.addr); The assignment of those two members (port, addr) are in the HttpSM.cc file (in attach_client_session function): ink_inet_copy(t_state.client_info.addr, netvc-get_remote_addr()); t_state.client_info.port = netvc-get_local_port(); the old code gave the right answer from the port member, and the new one gives us wrong answer fron the remote addr. I thought to fix it by rewrite the code get_remote_addr = get_local_addr (as in the patch that I attached to here) But it makes bugs in other places (redirect to another address). Or maybe it will be better to rewrite the TSHttpTxnClientIncomingPortGet function to the old version. was: In HttpSM.cc file (attach_client_session) there are two lines: ink_inet_copy(t_state.client_info.addr, netvc-get_remote_addr()); t_state.client_info.port = netvc-get_local_port(); instead of: ink_inet_copy(t_state.client_info.addr, netvc-get_local_addr()); t_state.client_info.port = netvc-get_local_port(); Wrong assignment of incoming address Key: TS-1127 URL: https://issues.apache.org/jira/browse/TS-1127 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 3.1.2 Reporter: Yakov Kopel Fix For: 3.1.4 Attachments: fix.patch Original Estimate: 1m Remaining Estimate: 1m There is a problem in the new version of trafficserverin the function (HttpSM.cc): TSHttpTxnClientIncomingPortGet The old code: return sm-t_state.client_info.port The new code: return ink_inet_get_port(sm-t_state.client_info.addr); The assignment of those two members (port, addr) are in the HttpSM.cc file (in attach_client_session function): ink_inet_copy(t_state.client_info.addr, netvc-get_remote_addr()); t_state.client_info.port = netvc-get_local_port(); the old code gave the right answer from the port member, and the new one gives us wrong answer fron the remote addr. I thought to fix it by rewrite the code get_remote_addr = get_local_addr (as in the patch that I attached to here) But it makes bugs in other places (redirect to another address). Or maybe it will be better to rewrite the TSHttpTxnClientIncomingPortGet function to the old version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1058) Intercept an HTTP client's request
[
https://issues.apache.org/jira/browse/TS-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yakov Kopel updated TS-1058:
Description:
I want that the trafficserver will give the client the response instead of the
server.
The trafficserver offers the INKHttpTxnIntercept api to do so, but it is not so
convenience to use it.
I want to use the regular flow of the trafficserver, and its regular parsing
commands.
The trafficserver's plugins examples also aren't using the INKHttpTxnIntercept
, but they rather using the rasing error method, and then they response the
request at the response hook.
So, this is whta i did.
On the global-hook at the TS_EVENT_HTTP_READ_REQUEST_HDR i raised
TS_EVENT_HTTP_ERROR.
I also added TS_HTTP_SEND_RESPONSE_HDR_HOOK and there i returned http response
with the KEEP-ALIVE header.
The problem is that the trafficserver is closing the connection although i
added to the response the KEEP-ALIVE header.
When the Trafficserver is trying to send response to the client, it terminate
the session after it.
Although I added the KEEP-ALIVE mime field - it didn't work.
The debug dump is looking like this:
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::state_api_callback, HTTP_API_CONTINUE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::state_api_callout, HTTP_API_CONTINUE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpSM::do_redirect]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4] adding
producer 'internal msg'
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4] adding
consumer 'user agent'
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) tunnel_run
started, p_arg is NULL
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4]
consumer_handler [user agent VC_EVENT_WRITE_COMPLETE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::tunnel_handler_ua, VC_EVENT_WRITE_COMPLETE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_cs) [4] session
closed
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_cs) [4] session
destroy
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::main_handler, HTTP_TUNNEL_EVENT_DONE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::tunnel_handler, HTTP_TUNNEL_EVENT_DONE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4] calling
plugin on hook TS_HTTP_TXN_CLOSE_HOOK at hook 0x3B97610
The Solution:
I'm adding a patch of functino that rasing the internal flag of KEEP-ALIVE, so
the trafficserver will realy believe us that we want to keep this connection
alive :)
Example for the usage of the new function:
// Tell the trafficserver to not close this connection (keep-alive)
TSHttpTxnCloseAfterResponse(txnp, 0);
was:
When the Trafficserver is trying to send response to the client, it terminate
the session after it.
Although I added the KEEP-ALIVE mime field - it didn't work.
The debug dump is looking like this:
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::state_api_callback, HTTP_API_CONTINUE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::state_api_callout, HTTP_API_CONTINUE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpSM::do_redirect]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4] adding
producer 'internal msg'
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4] adding
consumer 'user agent'
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) tunnel_run
started, p_arg is NULL
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4]
consumer_handler [user agent VC_EVENT_WRITE_COMPLETE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::tunnel_handler_ua, VC_EVENT_WRITE_COMPLETE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_cs) [4] session
closed
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_cs) [4] session
destroy
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::main_handler, HTTP_TUNNEL_EVENT_DONE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::tunnel_handler, HTTP_TUNNEL_EVENT_DONE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG:
[jira] [Updated] (TS-1057) Expose internal Base64 Encoding / Decoding
[ https://issues.apache.org/jira/browse/TS-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yakov Kopel updated TS-1057: Attachment: (was: patch.diff) Expose internal Base64 Encoding / Decoding -- Key: TS-1057 URL: https://issues.apache.org/jira/browse/TS-1057 Project: Traffic Server Issue Type: Bug Components: TS API Affects Versions: 3.1.1 Reporter: Yakov Kopel Priority: Minor Labels: patch Fix For: 3.1.2 Original Estimate: 24h Remaining Estimate: 24h Expose internal Base64 Encoding / Decoding for using in the plugins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1057) Expose internal Base64 Encoding / Decoding
[ https://issues.apache.org/jira/browse/TS-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yakov Kopel updated TS-1057: Attachment: patch.diff Expose internal Base64 Encoding / Decoding -- Key: TS-1057 URL: https://issues.apache.org/jira/browse/TS-1057 Project: Traffic Server Issue Type: Bug Components: TS API Affects Versions: 3.1.1 Reporter: Yakov Kopel Priority: Minor Labels: patch Fix For: 3.1.2 Attachments: patch.diff Original Estimate: 24h Remaining Estimate: 24h Expose internal Base64 Encoding / Decoding for using in the plugins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1058) Keep-Alive is not working
[
https://issues.apache.org/jira/browse/TS-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yakov Kopel updated TS-1058:
Summary: Keep-Alive is not working (was: Kepp-Alive is not working)
Keep-Alive is not working
-
Key: TS-1058
URL: https://issues.apache.org/jira/browse/TS-1058
Project: Traffic Server
Issue Type: Bug
Components: TS API
Affects Versions: 3.1.1
Reporter: Yakov Kopel
Labels: patch
Fix For: 3.1.2
Attachments: patch.diff
Original Estimate: 24h
Remaining Estimate: 24h
When the Trafficserver is trying to send response to the client, it terminate
the session after it.
Although I added the KEEP-ALIVE mime field - it didn't work.
The debug dump is looking like this:
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::state_api_callback, HTTP_API_CONTINUE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::state_api_callout, HTTP_API_CONTINUE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpSM::do_redirect]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4]
adding producer 'internal msg'
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4]
adding consumer 'user agent'
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel)
tunnel_run started, p_arg is NULL
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4]
consumer_handler [user agent VC_EVENT_WRITE_COMPLETE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::tunnel_handler_ua, VC_EVENT_WRITE_COMPLETE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_cs) [4] session
closed
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_cs) [4] session
destroy
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::main_handler, HTTP_TUNNEL_EVENT_DONE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::tunnel_handler, HTTP_TUNNEL_EVENT_DONE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4] calling
plugin on hook TS_HTTP_TXN_CLOSE_HOOK at hook 0x3B97610
The Solution:
I'm adding a patch of functino that rasing the internal flag of KEEP-ALIVE,
so the trafficserver will realy believe us that we want to keep this
connection alive :) .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1058) Keep-Alive is not working
[
https://issues.apache.org/jira/browse/TS-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yakov Kopel updated TS-1058:
Attachment: patch.diff
Keep-Alive is not working
-
Key: TS-1058
URL: https://issues.apache.org/jira/browse/TS-1058
Project: Traffic Server
Issue Type: Bug
Components: TS API
Affects Versions: 3.1.1
Reporter: Yakov Kopel
Labels: patch
Fix For: 3.1.2
Attachments: patch.diff
Original Estimate: 24h
Remaining Estimate: 24h
When the Trafficserver is trying to send response to the client, it terminate
the session after it.
Although I added the KEEP-ALIVE mime field - it didn't work.
The debug dump is looking like this:
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::state_api_callback, HTTP_API_CONTINUE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::state_api_callout, HTTP_API_CONTINUE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpSM::do_redirect]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4]
adding producer 'internal msg'
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4]
adding consumer 'user agent'
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel)
tunnel_run started, p_arg is NULL
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4]
consumer_handler [user agent VC_EVENT_WRITE_COMPLETE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::tunnel_handler_ua, VC_EVENT_WRITE_COMPLETE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_cs) [4] session
closed
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_cs) [4] session
destroy
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::main_handler, HTTP_TUNNEL_EVENT_DONE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::tunnel_handler, HTTP_TUNNEL_EVENT_DONE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4] calling
plugin on hook TS_HTTP_TXN_CLOSE_HOOK at hook 0x3B97610
The Solution:
I'm adding a patch of functino that rasing the internal flag of KEEP-ALIVE,
so the trafficserver will realy believe us that we want to keep this
connection alive :) .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1058) Kepp-Alive is not working
[
https://issues.apache.org/jira/browse/TS-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yakov Kopel updated TS-1058:
Summary: Kepp-Alive is not working (was: Forced Dissconection)
Kepp-Alive is not working
-
Key: TS-1058
URL: https://issues.apache.org/jira/browse/TS-1058
Project: Traffic Server
Issue Type: Bug
Components: TS API
Affects Versions: 3.1.1
Reporter: Yakov Kopel
Labels: patch
Fix For: 3.1.2
Attachments: patch.diff
Original Estimate: 24h
Remaining Estimate: 24h
When the Trafficserver is trying to send response to the client, it terminate
the session after it.
Although I added the KEEP-ALIVE mime field - it didn't work.
The debug dump is looking like this:
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::state_api_callback, HTTP_API_CONTINUE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::state_api_callout, HTTP_API_CONTINUE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpSM::do_redirect]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4]
adding producer 'internal msg'
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4]
adding consumer 'user agent'
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel)
tunnel_run started, p_arg is NULL
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4]
consumer_handler [user agent VC_EVENT_WRITE_COMPLETE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::tunnel_handler_ua, VC_EVENT_WRITE_COMPLETE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_cs) [4] session
closed
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_cs) [4] session
destroy
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::main_handler, HTTP_TUNNEL_EVENT_DONE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::tunnel_handler, HTTP_TUNNEL_EVENT_DONE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4] calling
plugin on hook TS_HTTP_TXN_CLOSE_HOOK at hook 0x3B97610
The Solution:
I'm adding a patch of functino that rasing the internal flag of KEEP-ALIVE,
so the trafficserver will realy believe us that we want to keep this
connection alive :) .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1058) Keep-Alive is not working
[
https://issues.apache.org/jira/browse/TS-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yakov Kopel updated TS-1058:
Description:
When the Trafficserver is trying to send response to the client, it terminate
the session after it.
Although I added the KEEP-ALIVE mime field - it didn't work.
The debug dump is looking like this:
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::state_api_callback, HTTP_API_CONTINUE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::state_api_callout, HTTP_API_CONTINUE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpSM::do_redirect]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4] adding
producer 'internal msg'
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4] adding
consumer 'user agent'
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) tunnel_run
started, p_arg is NULL
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4]
consumer_handler [user agent VC_EVENT_WRITE_COMPLETE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::tunnel_handler_ua, VC_EVENT_WRITE_COMPLETE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_cs) [4] session
closed
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_cs) [4] session
destroy
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::main_handler, HTTP_TUNNEL_EVENT_DONE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::tunnel_handler, HTTP_TUNNEL_EVENT_DONE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4] calling
plugin on hook TS_HTTP_TXN_CLOSE_HOOK at hook 0x3B97610
The Solution:
I'm adding a patch of functino that rasing the internal flag of KEEP-ALIVE, so
the trafficserver will realy believe us that we want to keep this connection
alive :)
Example for the usage of the new function:
// Tell the trafficserver to not close this connection (keep-alive)
TSHttpTxnCloseAfterResponse(txnp, 0);
was:
When the Trafficserver is trying to send response to the client, it terminate
the session after it.
Although I added the KEEP-ALIVE mime field - it didn't work.
The debug dump is looking like this:
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::state_api_callback, HTTP_API_CONTINUE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::state_api_callout, HTTP_API_CONTINUE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpSM::do_redirect]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4] adding
producer 'internal msg'
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4] adding
consumer 'user agent'
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) tunnel_run
started, p_arg is NULL
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_tunnel) [4]
consumer_handler [user agent VC_EVENT_WRITE_COMPLETE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::tunnel_handler_ua, VC_EVENT_WRITE_COMPLETE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_cs) [4] session
closed
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_cs) [4] session
destroy
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::main_handler, HTTP_TUNNEL_EVENT_DONE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4]
[HttpSM::tunnel_handler, HTTP_TUNNEL_EVENT_DONE]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http_redirect)
[HttpTunnel::deallocate_postdata_copy_buffers]
[Dec 15 07:46:47.251] Server {0x2b8806ac9a80} DEBUG: (http) [4] calling
plugin on hook TS_HTTP_TXN_CLOSE_HOOK at hook 0x3B97610
The Solution:
I'm adding a patch of functino that rasing the internal flag of KEEP-ALIVE, so
the trafficserver will realy believe us that we want to keep this connection
alive :) .
Keep-Alive is not working
-
Key: TS-1058
URL: https://issues.apache.org/jira/browse/TS-1058
Project: Traffic Server
Issue Type: Bug
Components: TS API
Affects Versions: 3.1.1
Reporter: Yakov Kopel
Labels: patch
Fix For: 3.1.2
Attachments: patch.diff
Original Estimate: 24h
Remaining Estimate: 24h
When the Trafficserver is trying to send response to the client, it terminate
the session after
