Maybe rename "ClientProtoType" to "ClientProtocolStack" would be more
descriptive.
On Fri, Mar 7, 2014 at 10:16 AM, Yunkai Zhang wrote:
>
>
>
> On Fri, Mar 7, 2014 at 7:37 AM, Leif Hedstrom wrote:
>
>>
>> On Mar 6, 2014, at 7:25 PM, Alan M. Carroll
>> wrote:
>>
>> > Perhaps "scheme" for the H
On Fri, Mar 7, 2014 at 7:37 AM, Leif Hedstrom wrote:
>
> On Mar 6, 2014, at 7:25 PM, Alan M. Carroll
> wrote:
>
> > Perhaps "scheme" for the HTTP vs. HTTPS vs. SPDY - I think that's what
> the internal use. "Proto" and "Protocol" are somewhat vague.
>
> "scheme" is certainly the correct nomencla
On Mar 6, 2014, at 7:25 PM, Alan M. Carroll
wrote:
> Perhaps "scheme" for the HTTP vs. HTTPS vs. SPDY - I think that's what the
> internal use. "Proto" and "Protocol" are somewhat vague.
“scheme” is certainly the correct nomenclature according to e.g. RFC3986.
— leif
Github user asfgit closed the pull request at:
https://github.com/apache/trafficserver/pull/58
---
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 i
GitHub user manjeshnilange opened a pull request:
https://github.com/apache/trafficserver/pull/58
atscppapi: Added missing intercept files
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/manjeshnilange/trafficserver master
Alter
GitHub user piotrbulinski opened a pull request:
https://github.com/apache/trafficserver/pull/57
records.config fixes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/piotrbulinski/trafficserver master
Alternatively you can revie
Github user asfgit closed the pull request at:
https://github.com/apache/trafficserver/pull/56
---
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 i
We should have a JIRA ticket for this so that we can publish accurate change
logs and release notes
On Mar 6, 2014, at 12:47 PM, bri...@apache.org wrote:
> intercept support in atscppapi
>
>
> Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
> Commit: http://git-wip-us.apach
GitHub user manjeshnilange opened a pull request:
https://github.com/apache/trafficserver/pull/56
Fixed async http fetch to support headers and post body
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/manjeshnilange/trafficserve
Perhaps "scheme" for the HTTP vs. HTTPS vs. SPDY - I think that's what the
internal use. "Proto" and "Protocol" are somewhat vague.
Thursday, March 6, 2014, 12:01:55 AM, you wrote:
>> > But for plugins that using TSHttpConnect() API to do request, the Logging
>> > module can't know which protoco
I’ll start making notes [1] and in case of any problems, will ask questions on
IRC.
[1] https://gist.github.com/piotrbulinski/9396189
Cheers,
Piotr
On 28 Feb 2014, at 18:45, Piotr Bulinski wrote:
> After weekend (Tue+) I’ll be happy to give it a try (if it’s not completed
> before).
>
> On
GitHub user rwbarber2 opened a pull request:
https://github.com/apache/trafficserver/pull/55
TS-2614 - Response to invalid Content-Length for POST should be a 400 er...
...ror
Responds w/HTTP 400 Invalid Request when content length is < 0
Created new body_factory respons
12 matches
Mail list logo
