You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by chenglongwei <gi...@git.apache.org> on 2017/02/23 19:44:06 UTC

[GitHub] trafficserver issue #1483: HTTP Request Debugging Feature

GitHub user chenglongwei opened an issue:

    https://github.com/apache/trafficserver/issues/1483

    HTTP Request Debugging Feature

    ### Goals
    HTTP request debugging feature in ATS core can help ATS DevOps to quickly locate an issue at development, staging or production environments. Users can specify a single request they want to debug by marking it with a cookie. This feature logs the HTTP headers of the debugged request and its response before and after each plugin execution for each hook. This will allow engineers to identify issues due to plugin bugs and help them make sense of various changes happening throughout the request/response pipe.
    
    ### Specifications
    Only allow certain IPs to use this feature.
    For security reason, the IPs allowed to use this feature can be configured in a file debuggable_ips.config.
    
    Specify the debugging request with a cookie \u201c__ts_debug=on\u201d.
    This is added to cookie to specify that this request is to be debugged and headers are collected to be logged before and after executing each plugin at every hook.
    
    ### Proposed design
    
    ![httprequestdebuggingproposal_v3](https://cloud.githubusercontent.com/assets/7145562/23275886/014b66e4-f9bd-11e6-8559-23178659cea8.png)
    
    1. Make a specified request to debug this request and its response. 
    2. Before and after each plugin execution for each hook, ATS collects the hdrs (HTTP headers) of the debugged request and its response. A blacklist of headers (Cookie, Set-Cookie, Authorization, etc) could be used to avoid sensitive information going to logs.
    3. Log the debug information to a log file (Or other implementations).


----

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] trafficserver issue #1483: HTTP Request Debugging Feature

Posted by chenglongwei <gi...@git.apache.org>.
Github user chenglongwei commented on the issue:

    https://github.com/apache/trafficserver/issues/1483
  
    @danobi It could be. But the feature I proposed is mainly to debug plugins. This feature will log headers before and after each plugin execution. As respect to header logging for 4xx/5xx, it only needs to do logging after accept response from origin server.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] trafficserver issue #1483: HTTP Request Debugging Feature

Posted by chenglongwei <gi...@git.apache.org>.
Github user chenglongwei commented on the issue:

    https://github.com/apache/trafficserver/issues/1483
  
    Hi @zwoop @jpeach @SolidWallOfCode , could you give some feedbacks. This debug feature is very useful when dealing with plugin-related bugs and help us make sense of various changes happening throughout trafficserver.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] trafficserver issue #1483: HTTP Request Debugging Feature

Posted by danobi <gi...@git.apache.org>.
Github user danobi commented on the issue:

    https://github.com/apache/trafficserver/issues/1483
  
    I wonder if there's a way to roll in header logging for 4xx/5xx transactions into this idea as well.
    See #1210. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] trafficserver issue #1483: HTTP Transaction Debugging Feature

Posted by chenglongwei <gi...@git.apache.org>.
Github user chenglongwei commented on the issue:

    https://github.com/apache/trafficserver/issues/1483
  
    #1624 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---