It does whatever is in remap. So if you choose to make a request to /foo
and you have a remap to https://www.foo.com/ that will be an outgoing HTTPS
connection.
Brian
On Sunday, March 27, 2016, Dk Jack wrote:
> Does atscppapi::AsyncFetch support output https connections? Haven't tried
Does atscppapi::AsyncFetch support output https connections? Haven't tried
it yet. The documentation is not clear if its supported or not. Thanks.
-D
Github user asfgit closed the pull request at:
https://github.com/apache/trafficserver/pull/399
---
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 christoph-k86 opened a pull request:
https://github.com/apache/trafficserver/pull/399
Adding patch mentioned in https://issues.apache.org/jira/browse/TS-4009
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/christoph
Github user asfgit closed the pull request at:
https://github.com/apache/trafficserver/pull/165
---
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 jacksontj opened a pull request:
https://github.com/apache/trafficserver/pull/165
Add some tests around https certificate selection
Primarily around certificate loading since there were some questions
brought up in #121
You can merge this pull request into a Git
here is proxy.process.spdy.total_streams decremented?
>>
>> Total stats are normally not decremented and are a total count since the
>> system has been running or since the last time the stats were reset. We
>> don't want to decrement it and there is anothe
t. We
>don't want to decrement it and there is another stat to see the number of
>active streams.
>
>>
>> Where is proxy.process.https.connection_count decremented? Why is it
>>persistent? If it's measuring the total number of https connections
>>accepted, where
> persistent? If it's measuring the total number of https connections accepted,
> where is proxy.process.http.connection_count?
There is a proxy.process.http.total_client_connections already. After the
commit I was thinking that proxy.process.https.connection_cou
On May 27, 2014, at 9:14 AM, Sudheer Vinukonda wrote:
>
>
> On 5/27/14, 8:47 AM, "James Peach" wrote:
>
>> On May 27, 2014, at 7:33 AM, Sudheer Vinukonda
>> wrote:
>>
>>>
>>>
>>> On 5/26/14, 6:00 PM, "James Peach" wrote:
>>>
Bryan,
How are you expecting proxy.process.ssl
sion accept timestamp.
>
>>> What does proxy.process.spdy.total_time mean, and how would I use it?
>>>
>>> Why does proxy.process.ssl.total_success_handshake_count only count
>>> successes? What about failed handshakes?
>>>
oxy.process.ssl.total_success_handshake_count only count
>> successes? What about failed handshakes?
>>
>> Where is proxy.process.spdy.total_streams decremented?
>>
>> Where is proxy.process.https.connection_count decremented? Why is it
>> persistent? If it's measur
On May 27, 2014, at 6:47 AM, Alan M. Carroll
wrote:
> James,
>
> Monday, May 26, 2014, 8:00:59 PM, you wrote:
>
>> Where is proxy.process.spdy.total_streams decremented?
>
> I don't think it is - it is counting the total number of streams, which can
> only increase. The "ACTIVE" variants cou
esses? What about failed handshakes?
>
>Where is proxy.process.spdy.total_streams decremented?
>
>Where is proxy.process.https.connection_count decremented? Why is it
>persistent? If it's measuring the total number of https connections
>accepted, where is proxy.process.http.connection_count?
>
>
James,
Monday, May 26, 2014, 8:00:59 PM, you wrote:
> Where is proxy.process.spdy.total_streams decremented?
I don't think it is - it is counting the total number of streams, which can
only increase. The "ACTIVE" variants count the number of objects currently
extant. This is parallel to things
does proxy.process.ssl.total_success_handshake_count only count successes?
What about failed handshakes?
Where is proxy.process.spdy.total_streams decremented?
Where is proxy.process.https.connection_count decremented? Why is it
persistent? If it's measuring the total number of https connections accepted,
Please whenever possible, rebase before pushing.
Otherwise it's quite easy for reviewers to miss a commit..
- Original Message -
> Merge branch 'master' of
> https://git-wip-us.apache.org/repos/asf/trafficserver
>
>
> Project: http://git-wip-us.apache.or
- Original Message -
> Hi All,
> Can ATS cache https requests?
if it's terminating them, then yes, otherwise, no.
(You'd have to set-up a transparent proxy and dynamically sign certificates for
each site your client machines are accessing. We haven't automated th
Hi All,
Can ATS cache https requests?
Regards,
Karthick
Thanks for the highlight, it sounds more difficult to me since i just
started with this caching field. But since now most sites are requiring
HTTPS connection (even google search is using https) not to mention social
sites and most mobile devices are recommend to use https before fallback to
http
On 4/15/13 1:11 PM, n...@apache.org wrote:
Merge https://git-wip-us.apache.org/repos/asf/trafficserver
Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
Commit: http://git-wip-us.apache.org/repos/asf/trafficserver/commit/41f1c2e1
Tree: http://git-wip-us.apache.org/repos/asf
On Feb 6, 2013, at 7:21 AM, Leif Hedstrom wrote:
> On 2/6/13 12:35 AM, oksana fishman wrote:
>> I can see a certificate, for example.
>> How https traffic can be seen by ATS plugin?
>
> You mean the SSL handshake? That would be Layer 5, not Layer 7 (HTTPS). I
> don&#x
On 2/6/13 12:35 AM, oksana fishman wrote:
I can see a certificate, for example.
How https traffic can be seen by ATS plugin?
You mean the SSL handshake? That would be Layer 5, not Layer 7 (HTTPS). I
don't think we expose any APIs for a plugin to intercept or participate in
the handshake
I can see a certificate, for example.
How https traffic can be seen by ATS plugin?
On Tue, Feb 5, 2013 at 6:08 AM, Leif Hedstrom wrote:
>
> On 2/4/13 9:02 AM, oksana fishman wrote:
>>
>> Hi,
>>
>> Thank you for quick response
>> I don't mean level 3 and
On 2/4/13 9:02 AM, oksana fishman wrote:
Hi,
Thank you for quick response
I don't mean level 3 and 4.
I mean HTTPS traffic
How are you going to see anything in the HTTPS requests without doing SSL
termination on the proxy server?
-- Leif
Hi,
Thank you for quick response
I don't mean level 3 and 4.
I mean HTTPS traffic
On Mon, Feb 4, 2013 at 4:48 PM, Leif Hedstrom wrote:
> On 2/4/13 5:20 AM, oksana fishman wrote:
>
>> Hi,
>> Is it possible to configure a trafficserver to work with HTTPS traffic?
>>
On 2/4/13 5:20 AM, oksana fishman wrote:
Hi,
Is it possible to configure a trafficserver to work with HTTPS traffic?
To forward it to the server / parse it ? Only parse the visible fields, not
to perform SSL termination ?
What visible fields? You mean on Level 3 and 4 ?
-- Leif
Please add me
-sun
On Wed, May 5, 2010 at 1:36 PM, dianes wrote:
> Add me too please :)
>
> -diane
>
>
> Leif Hedstrom wrote:
>>
>> Hi all,
>>
>> I'm going to request that we get https://blogs.apache.org/trafficserver/
>> created, but part o
Add me too please :)
-diane
Leif Hedstrom wrote:
Hi all,
I'm going to request that we get https://blogs.apache.org/trafficserver/
created, but part of this process, I need to know who wants access. This
is yet another account creation process :). All committers are welcome
to blog
yes please.
miles
On May 3, 2010, at 9:20 PM, Leif Hedstrom wrote:
Hi all,
I'm going to request that we get https://blogs.apache.org/trafficserver/
created, but part of this process, I need to know who wants access.
This
is yet another account creation process :). All committer
On 05/04/2010 06:20 AM, Leif Hedstrom wrote:
I need to know who wants access.
Count me in.
Seems that wiki works for all domains.
Regards
--
^TM
Hi all,
I'm going to request that we get https://blogs.apache.org/trafficserver/
created, but part of this process, I need to know who wants access. This
is yet another account creation process :). All committers are welcome
to blog about TS, of course.
Cheers,
-- leif
[
https://issues.apache.org/jira/browse/TS-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848864#action_12848864
]
James Henderson commented on TS-147:
I seem to be having the same issue, but with a st
[
https://issues.apache.org/jira/browse/TS-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830579#action_12830579
]
Jason Giedymin commented on TS-147:
---
It's possible that TS is trying to verify m
Reverse Proxy Mode + Cache crashes / Segmentation fault when using HTTPS
dynamic pages, Static Fine
---
Key: TS-147
URL: https://issues.apache.org/jira/browse/TS-147
[
https://issues.apache.org/jira/browse/TS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
George Paul resolved TS-123.
Resolution: Fixed
Fix Version/s: 2.0.0
This patch 'TS123_patch1.diff' has been committed to
[
https://issues.apache.org/jira/browse/TS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806235#action_12806235
]
Jason Giedymin commented on TS-123:
---
Patch tested, and works.
Thanks George
&g
[
https://issues.apache.org/jira/browse/TS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806229#action_12806229
]
George Paul commented on TS-123:
This patch 'TS123_patch1.diff' has been committ
[
https://issues.apache.org/jira/browse/TS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
George Paul updated TS-123:
---
Attachment: TS123_patch1.diff
This patch 'TS123_patch1.diff' fixes incorrect check for http being
[
https://issues.apache.org/jira/browse/TS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
George Paul reassigned TS-123:
--
Assignee: George Paul
> Http fails but https works, when running with the TS process stack, works
>
[
https://issues.apache.org/jira/browse/TS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806211#action_12806211
]
Jason Giedymin commented on TS-123:
---
Is Y! running the current trunk on their produc
Http fails but https works, when running with the TS process stack, works when
using 'traffic_server'"
--
Key: TS-123
URL: https://issues.apache.
42 matches
Mail list logo
