[GitHub] trafficserver pull request: Modified the plugin to add back the Ra...

[jrushf1239k]

Github user jrushf1239k commented on the pull request:

    https://github.com/apache/trafficserver/pull/297#issuecomment-141536125
  
    That’s why I added it back as ‘Range’, so that it would be seamless 
for those using custom logs.  Otherwise they’d have to read the source code 
and/or it’s documentation to know to use @Range.
    
    Thanks
    --
    John J. Rushford
    IPCDN Engineering
    1400 Wewatta Street, Denver Colorado 80202
    john_rushf...@cable.comcast.com
    
    
    
    
    
    
    
    
    
    
    
    From: sudheerv <notificati...@github.com<mailto:notificati...@github.com>>
    Reply-To: apache/trafficserver 
<re...@reply.github.com<mailto:re...@reply.github.com>>
    Date: Friday, September 18, 2015 at 12:23 PM
    To: apache/trafficserver 
<trafficser...@noreply.github.com<mailto:trafficser...@noreply.github.com>>
    Cc: John Rushford 
<john_rushf...@cable.comcast.com<mailto:john_rushf...@cable.comcast.com>>
    Subject: Re: [trafficserver] Modified the plugin to add back the Range 
request header at the TS_HT… (#297)
    
    
    @jpeach<https://github.com/jpeach> : I agree - but, one issue I could see 
in renaming Range to @Range<https://github.com/Range>, is that, it's not 
transparent to custom logging configuration (the operators need to know to log 
@Range<https://github.com/Range> instead of Range). Whereas, re-adding the 
Range header back makes it seamlessly work for operators wanting to log Range 
header.
    
    —
    Reply to this email directly or view it on 
GitHub<https://github.com/apache/trafficserver/pull/297#issuecomment-141525465>.



---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---