[jira] [Created] (TS-2531) The default remap rule doesn't match a forward proxy request

2014-01-25 Thread Bryan Call (JIRA)
Bryan Call created TS-2531:
--

 Summary: The default remap rule doesn't match a forward proxy 
request
 Key: TS-2531
 URL: https://issues.apache.org/jira/browse/TS-2531
 Project: Traffic Server
  Issue Type: Bug
  Components: HTTP
Reporter: Bryan Call


when doing a forward proxy request it won't math the default rule, but will 
match other rules that specify the hostname.

Example request:
GET http://foo.yahoo.com HTTP/1.1
Host: foo.yahoo.com

remap.config:
map / http://www.yahoo.com

Response:
HTTP/1.1 404 Not Found
...



However, this works:

remap.config:
map http://foo.yahoo.com http://www.yahoo.com




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (TS-2504) Fix crypto.m4 when detect openssl library in 64bit OS

2014-01-25 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/TS-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881985#comment-13881985
 ] 

ASF subversion and git services commented on TS-2504:
-

Commit 0f4c7b8ffb26326dbd2cde77c986726ffe8f0552 in branch refs/heads/master 
from [~yunkai]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=0f4c7b8 ]

TS-2504: Set LDFLAGS/CPPFLAGS properly in crypto.m4

At the end of AX_CHECK_OPENSSL(), LDFLAGS/CPPFLAGS/LIBS variables
will be reset, so there is no sense in setting these variables within
AX_CHECK_OPENSSL(). We should set them outside of it.

Signed-off-by: Yunkai Zhang 


> Fix crypto.m4 when detect openssl library in 64bit OS
> -
>
> Key: TS-2504
> URL: https://issues.apache.org/jira/browse/TS-2504
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Build
>Reporter: Yunkai Zhang
>Assignee: James Peach
> Fix For: 4.2.0
>
>
> From [~jamespeach]:
> {quote}
> Yunkai Zhang can you split 
> 0007-Fix-crypto.m4-when-detect-openssl-library-in-64bit-O.V2.patch into a 
> separate Jira ticket? 
> Shall we use 
> http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=blob_plain;f=m4/ax_check_openssl.m4
>  to improve OpenSSL detection?
> {quote}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Resolved] (TS-2504) Fix crypto.m4 when detect openssl library in 64bit OS

2014-01-25 Thread Yunkai Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yunkai Zhang resolved TS-2504.
--

Resolution: Fixed

Fixed.

> Fix crypto.m4 when detect openssl library in 64bit OS
> -
>
> Key: TS-2504
> URL: https://issues.apache.org/jira/browse/TS-2504
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Build
>Reporter: Yunkai Zhang
>Assignee: James Peach
> Fix For: 4.2.0
>
>
> From [~jamespeach]:
> {quote}
> Yunkai Zhang can you split 
> 0007-Fix-crypto.m4-when-detect-openssl-library-in-64bit-O.V2.patch into a 
> separate Jira ticket? 
> Shall we use 
> http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=blob_plain;f=m4/ax_check_openssl.m4
>  to improve OpenSSL detection?
> {quote}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (TS-2394) We need a performance tuning document

2014-01-25 Thread JIRA

[ 
https://issues.apache.org/jira/browse/TS-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882048#comment-13882048
 ] 

Igor Galić commented on TS-2394:


Yeah, the above commit message says it's just a stub, I haven't had time to 
actually sit down and flesh out a sensible document ­— or even just its scope.

> We need a performance tuning document
> -
>
> Key: TS-2394
> URL: https://issues.apache.org/jira/browse/TS-2394
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Documentation
>Reporter: Igor Galić
> Fix For: Docs
>
>
> Traffic Server is a complex beast, we need a document that unifies and 
> links-back to all the different options that have an affect on its 
> performance.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Updated] (TS-2210) add API to get access to the client cert in the SSL Net VC

2014-01-25 Thread kang li (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

kang li updated TS-2210:


Attachment: 2210.diff

Add api to export SSL client certificate information, include client 
certificate verify result, issuer DN, subject DN, etc.

> add API to get access to the client cert in the SSL Net VC
> --
>
> Key: TS-2210
> URL: https://issues.apache.org/jira/browse/TS-2210
> Project: Traffic Server
>  Issue Type: Improvement
>  Components: SSL, TS API
>Reporter: Bryan Call
> Fix For: 4.2.0
>
> Attachments: 2210.diff
>
>
> In SSLNetVConnection SSL_get_peer_certificate(ssl) is called and client_cert 
> is set.  There is a request from Brian France to get access to the client 
> cert.
> He wants to be able to call X509_NAME_oneline(), X509_get_subject_name(), and 
> X509_get_issuer_name() on the cert.
> Where the cert is set in the code:
> iocore/net/SSLNetVConnection.cc:499:client_cert = 
> SSL_get_peer_certificate(ssl);



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)