Github user zizhong commented on the pull request:
https://github.com/apache/trafficserver/pull/301#issuecomment-164656248
@jpeach , I noticed you have changed the some details of the last commit.
Thanks for your help. However, there is a bug that you introduced with the
changes.
Github user asfgit closed the pull request at:
https://github.com/apache/trafficserver/pull/301
---
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
Github user zizhong commented on the pull request:
https://github.com/apache/trafficserver/pull/301#issuecomment-164642165
@jpeach Thanks for the useful comments. I've made a new commit on your
suggestions. Would you mind having another look?
---
If your project is set up for it, you
I've prepared a release for 6.0.1 (RC1) which is the next bug fix version of
Apache Traffic Server. This is detailed in our Release Management document:
https://cwiki.apache.org/confluence/display/TS/Release+Management
Release notes for 6.0.1:
https://issues.apache.org/jira/secure/ReleaseNote.
Github user asfgit closed the pull request at:
https://github.com/apache/trafficserver/pull/366
---
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
Github user zwoop commented on the pull request:
https://github.com/apache/trafficserver/pull/371#issuecomment-164589466
I'm going to land this, unless there are other review concerns. (Gancho
fixed a few number of issues that was reported outside of this PR already).
---
If your pro
Github user zwoop commented on the pull request:
https://github.com/apache/trafficserver/pull/376#issuecomment-164572673
+1, please commit :).
---
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
GitHub user jplevyak opened a pull request:
https://github.com/apache/trafficserver/pull/376
Fix clang analysis issue in the RamCache*.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jplevyak/trafficserver TS-4053-2
Alternative
Github user asfgit closed the pull request at:
https://github.com/apache/trafficserver/pull/369
---
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
GitHub user cschombu opened a pull request:
https://github.com/apache/trafficserver/pull/375
TS-4070 RemapProcessor Forward Mapping with Recv Port failing with TSâ¦
â¦-2157 changes
During the rework of RemapProcessor.cc, RemapProcessor::setup_for_remap()
as part of the
Github user sudheerv commented on the pull request:
https://github.com/apache/trafficserver/pull/351#issuecomment-164477764
Cool, thanks!
---
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
Github user bgaff commented on the pull request:
https://github.com/apache/trafficserver/pull/351#issuecomment-164477595
That's correct since both use fetchsm if just works like a normal http 1.1
request, as that's what fetch sm is. I've verified this functionality.
---
If your proje
Github user sudheerv commented on the pull request:
https://github.com/apache/trafficserver/pull/351#issuecomment-164477130
@bgaff - Thanks, I'd have to double check though that the change made
automatically handles a H2/SPDY upload. There's no Content-Length, nor even a
TE header in
GitHub user oknet opened a pull request:
https://github.com/apache/trafficserver/pull/374
TS-4075: add a state check for sslHandshakeHookState
Add a state check for sslHandshakeHookState after PreAcceptHookState
checking in sslServerHandShakeEvent().
and modify the codes in reen
14 matches
Mail list logo
