[jira] [Closed] (HTTPASYNC-171) Async http post with apache client 5.3

2024-01-29 Thread tassadar (Jira)


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

tassadar closed HTTPASYNC-171.
--

thanks Oleg, it worked

> Async http post with apache client 5.3
> --
>
> Key: HTTPASYNC-171
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-171
> Project: HttpComponents HttpAsyncClient
>  Issue Type: Bug
>Reporter: tassadar
>Priority: Major
>
> I constructed an async client with:
> {code:java}
> private val httpclient = HttpAsyncClients.custom()
> .setConnectionManager(connectionManager)
> .build();{code}
> {color:#172b4d}And i noticed that the Content-Length header is not supplied. 
> Invastigating i saw that all the requesta were made as http 2.0, so i tried 
> to force an http 1.1 request:
> {color}
> {code:java}
> request.setVersion(HttpVersion.HTTP_1_1)
> localContext.setProtocolVersion(HttpVersion.HTTP_1_1){code}
> but it didn't worked, still the request were made as http 2.0. Trying to 
> investigate further i noticed that even if the{color:#172b4d} 
> H2RequestContent interceptor is able to manage the http 1.1 request 
> (delegating it to super) the 
> {color}AbstractH2StreamMultiplexer.{color:#172b4d}getProtocolVersion() 
> involved in the process always returns {color}http_2:
> {code:java}
> @Override
> public ProtocolVersion getProtocolVersion() {
> return HttpVersion.HTTP_2;
> }{code}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org



Re: [PR] SNI support improvements [httpcomponents-client]

2024-01-29 Thread via GitHub


ok2c commented on PR #543:
URL: 
https://github.com/apache/httpcomponents-client/pull/543#issuecomment-1914713091

   @arturobernalg Please take a look.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org



[PR] SNI support improvements [httpcomponents-client]

2024-01-29 Thread via GitHub


ok2c opened a new pull request, #543:
URL: https://github.com/apache/httpcomponents-client/pull/543

   * Connection route info now request URI authority
   * The default route planner and connections managers now take request URI 
authority when calculating the connection route and when pooling and re-using 
connections


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org



[jira] [Resolved] (HTTPCLIENT-751) ProtocolSocketFactory to upgrade an unsecured connection to secured via TLS

2024-01-29 Thread Oleg Kalnichevski (Jira)


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

Oleg Kalnichevski resolved HTTPCLIENT-751.
--
Resolution: Fixed

> ProtocolSocketFactory to upgrade an unsecured connection to secured via TLS
> ---
>
> Key: HTTPCLIENT-751
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-751
> Project: HttpComponents HttpClient
>  Issue Type: New Feature
> Environment: Coded for Java 1.4.2, but interested parties should be 
> able to make it work for less than that.
>Reporter: Stephen O'Neil Butler
>Priority: Minor
> Fix For: 5.4-alpha2
>
> Attachments: TLSProtocolSocketFactory.java
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> HTTP allows a client to upgrade its connection from an unsecured one to a 
> secured one via the Upgrade header. This protocol component implements a 
> mandatory upgrade. From RFC2817, section 3.2:
> >> OPTIONS * HTTP/1.1
> >> Host: example.bank.com
> >> Upgrade: TLS/1.0
> >> Connection: Upgrade
> >>
> << HTTP/1.1 101 Switching Protocols
> << Upgrade: TLS/1.0, HTTP/1.1
> << Connection: Upgrade
> << 
> -- send and complete the TLS handshake
> -- server answers the original OPTIONS request
> << HTTP/1.1 200 OK
> << Date: Sun, 17 Feb 2008 17:23:35 GMT
> << Server: Apache
> << Content-Length: 0
> << Content-Type: text/plain
> <<
> My reason for developing this protocol socket factory was to support secure 
> IPP over the standard IPP port.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org



[jira] [Commented] (HTTPCLIENT-751) ProtocolSocketFactory to upgrade an unsecured connection to secured via TLS

2024-01-29 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811870#comment-17811870
 ] 

ASF subversion and git services commented on HTTPCLIENT-751:


Commit 3235f009d5673536be5c668df409ac3f83808d89 in httpcomponents-client's 
branch refs/heads/master from Oleg Kalnichevski
[ https://gitbox.apache.org/repos/asf?p=httpcomponents-client.git;h=3235f009d ]

HTTPCLIENT-751: Support for RFC 2817 (Upgrading to TLS Within HTTP/1.1)


> ProtocolSocketFactory to upgrade an unsecured connection to secured via TLS
> ---
>
> Key: HTTPCLIENT-751
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-751
> Project: HttpComponents HttpClient
>  Issue Type: New Feature
> Environment: Coded for Java 1.4.2, but interested parties should be 
> able to make it work for less than that.
>Reporter: Stephen O'Neil Butler
>Priority: Minor
> Fix For: 5.4-alpha2
>
> Attachments: TLSProtocolSocketFactory.java
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> HTTP allows a client to upgrade its connection from an unsecured one to a 
> secured one via the Upgrade header. This protocol component implements a 
> mandatory upgrade. From RFC2817, section 3.2:
> >> OPTIONS * HTTP/1.1
> >> Host: example.bank.com
> >> Upgrade: TLS/1.0
> >> Connection: Upgrade
> >>
> << HTTP/1.1 101 Switching Protocols
> << Upgrade: TLS/1.0, HTTP/1.1
> << Connection: Upgrade
> << 
> -- send and complete the TLS handshake
> -- server answers the original OPTIONS request
> << HTTP/1.1 200 OK
> << Date: Sun, 17 Feb 2008 17:23:35 GMT
> << Server: Apache
> << Content-Length: 0
> << Content-Type: text/plain
> <<
> My reason for developing this protocol socket factory was to support secure 
> IPP over the standard IPP port.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org



Re: [PR] HTTPCLIENT-751: Support for RFC 2817 (Upgrading to TLS Within HTTP/1.1) [httpcomponents-client]

2024-01-29 Thread via GitHub


ok2c merged PR #542:
URL: https://github.com/apache/httpcomponents-client/pull/542


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org



Re: [PR] TLS client endpoints to make use of JSSE Endpoint Identification by default [httpcomponents-core]

2024-01-29 Thread via GitHub


ok2c commented on PR #455:
URL: 
https://github.com/apache/httpcomponents-core/pull/455#issuecomment-1914352411

   @arturobernalg Please take a look. See 
https://issues.apache.org/jira/browse/HTTPCLIENT-2151 for details


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org



[PR] TLS client endpoints to make use of JSSE Endpoint Identification by default [httpcomponents-core]

2024-01-29 Thread via GitHub


ok2c opened a new pull request, #455:
URL: https://github.com/apache/httpcomponents-core/pull/455

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org