[jira] [Updated] (CXF-8220) The tag "http.status_code" is always 200 in server side tracing span, no matter what situation

[Jianshao Wu (Jira)]

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

Jianshao Wu updated CXF-8220:
-
Attachment: cxf-test.zip

> The tag "http.status_code" is always 200 in server side tracing span, no 
> matter what situation 
> ---
>
> Key: CXF-8220
> URL: https://issues.apache.org/jira/browse/CXF-8220
> Project: CXF
>  Issue Type: Bug
>  Components: Tracing
>Affects Versions: 3.3.4
>Reporter: Jianshao Wu
>Priority: Major
> Attachments: cxf-test.zip
>
>
> The tag "http.status_code" is always 200 in server side tracing span. I 
> investigated source code, found the following code in the method 
> "handleMessage" of  the class 
> "org.apache.cxf.tracing.opentracing.OpenTracingStopInterceptor " :
> {code:java}
>  Integer responseCode = (Integer)message.get(Message.RESPONSE_CODE);
>  if (responseCode == null) {
>  responseCode = 200;
>  }{code}
> The phase of this interceptor is PRE_MARSHAL, in this phase, the responseCode 
> is not put yet. Maybe this interceptor should be bound to another appropriate 
> phase.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (CXF-8223) Be able to read empty entity from a Response with 202

[Freeman Yue Fang (Jira)]

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

Freeman Yue Fang reassigned CXF-8223:
-

Assignee: Freeman Yue Fang

> Be able to read empty entity from a Response with 202
> -
>
> Key: CXF-8223
> URL: https://issues.apache.org/jira/browse/CXF-8223
> Project: CXF
>  Issue Type: Improvement
>  Components: JAX-RS
> Environment: JAXRS client can read empty entity from a Response with 
> 200, but can't do the similar from a Response with 202(HTTP ACCEPTED). The 
> reason is that currently CXF consider a 202 return as oneway or partial 
> response of WS-RM|WS-ADDRESSING, but this isn't always the case for JAXRS 
> response. We need to introduce a context property(the default value should 
> keep the behavior as before) so that RS client can explicitly specify that RS 
> client want to read the empty entity even with 202 response code.
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CXF-8223) Be able to read empty entity from a Response with 202

[Freeman Yue Fang (Jira)]

Freeman Yue Fang created CXF-8223:
-

 Summary: Be able to read empty entity from a Response with 202
 Key: CXF-8223
 URL: https://issues.apache.org/jira/browse/CXF-8223
 Project: CXF
  Issue Type: Improvement
  Components: JAX-RS
 Environment: JAXRS client can read empty entity from a Response with 
200, but can't do the similar from a Response with 202(HTTP ACCEPTED). The 
reason is that currently CXF consider a 202 return as oneway or partial 
response of WS-RM|WS-ADDRESSING, but this isn't always the case for JAXRS 
response. We need to introduce a context property(the default value should keep 
the behavior as before) so that RS client can explicitly specify that RS client 
want to read the empty entity even with 202 response code.
Reporter: Freeman Yue Fang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CXF-8222) OIDC Refresh Response: ID Token iat Claim MUST represent the time that the new ID Token is issued

[Alexey Markevich (Jira)]

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

Alexey Markevich updated CXF-8222:
--
Description: according to 
https://openid.net/specs/openid-connect-core-1_0.html#RefreshTokenResponse

> OIDC Refresh Response: ID Token iat Claim MUST represent the time that the 
> new ID Token is issued
> -
>
> Key: CXF-8222
> URL: https://issues.apache.org/jira/browse/CXF-8222
> Project: CXF
>  Issue Type: Bug
>  Components: JAX-RS Security
>Affects Versions: 3.3.6
>Reporter: Alexey Markevich
>Assignee: Alexey Markevich
>Priority: Major
>
> according to 
> https://openid.net/specs/openid-connect-core-1_0.html#RefreshTokenResponse



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CXF-8222) OIDC Refresh Response: ID Token iat Claim MUST represent the time that the new ID Token is issued

[Alexey Markevich (Jira)]

Alexey Markevich created CXF-8222:
-

 Summary: OIDC Refresh Response: ID Token iat Claim MUST represent 
the time that the new ID Token is issued
 Key: CXF-8222
 URL: https://issues.apache.org/jira/browse/CXF-8222
 Project: CXF
  Issue Type: Bug
  Components: JAX-RS Security
Affects Versions: 3.3.6
Reporter: Alexey Markevich
Assignee: Alexey Markevich






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CXF-8221) Upgrade Http Components Core and Client to 5.0

[Grzegorz Grzybek (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-8221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17044422#comment-17044422
 ] 

Grzegorz Grzybek commented on CXF-8221:
---

Just a reminder, that HttpClient/HttpCore 5 will *not* have OSGi support at 
all: 
https://github.com/apache/httpcomponents-client/commit/5797e2475a8709cdfe7faed16ef96c30cfa73976

> Upgrade Http Components Core and Client to 5.0
> --
>
> Key: CXF-8221
> URL: https://issues.apache.org/jira/browse/CXF-8221
> Project: CXF
>  Issue Type: Improvement
>Reporter: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.4.0
>
>
> Notable changes and features included in the 5.0 series are:
> * Support for the HTTP/2 protocol and conformance to requirements and
> recommendations of the latest HTTP/2 protocol specification documents
> (RFC 7540, RFC 7541.)
>   Supported features:
> ** HPACK header compression
> ** Stream multiplexing (client and server)
> ** Flow control
> ** Response push
> ** Message trailers
> ** Expect-continue handshake
> ** Connection validation (ping)
> ** Application-layer protocol negotiation (ALPN)
> ** TLS 1.2 security features
> * Improved conformance to requirements and recommendations of the
> latest HTTP/1.1 protocol specification documents (RFC 7230, RFC 7231)
> * New connection pool implementation with lax connection limit
> guarantees and better performance under higher concurrency due to
> absence of a global pool lock.
> * Support for Reactive Streams API [http://www.reactive-streams.org/]
> * Package name space changed to 'org.apache.hc.client5'.
> * Maven group id changed to 'org.apache.httpcomponents.client5'.
> HttpClient 5.0 releases can be co-located with earlier major versions
> on the same classpath due to the change in package names and Maven
> module coordinates.
> Download - 
> Release notes - <
> https://www.apache.org/dist/httpcomponents/httpclient/RELEASE_NOTES-5.0.x.txt



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CXF-8221) Upgrade Http Components Core and Client to 5.0

[Dennis Kieselhorst (Jira)]

Dennis Kieselhorst created CXF-8221:
---

 Summary: Upgrade Http Components Core and Client to 5.0
 Key: CXF-8221
 URL: https://issues.apache.org/jira/browse/CXF-8221
 Project: CXF
  Issue Type: Improvement
Reporter: Dennis Kieselhorst
 Fix For: 3.4.0


Notable changes and features included in the 5.0 series are:

* Support for the HTTP/2 protocol and conformance to requirements and
recommendations of the latest HTTP/2 protocol specification documents
(RFC 7540, RFC 7541.)

  Supported features:

** HPACK header compression
** Stream multiplexing (client and server)
** Flow control
** Response push
** Message trailers
** Expect-continue handshake
** Connection validation (ping)
** Application-layer protocol negotiation (ALPN)
** TLS 1.2 security features

* Improved conformance to requirements and recommendations of the
latest HTTP/1.1 protocol specification documents (RFC 7230, RFC 7231)

* New connection pool implementation with lax connection limit
guarantees and better performance under higher concurrency due to
absence of a global pool lock.

* Support for Reactive Streams API [http://www.reactive-streams.org/]

* Package name space changed to 'org.apache.hc.client5'.

* Maven group id changed to 'org.apache.httpcomponents.client5'.

HttpClient 5.0 releases can be co-located with earlier major versions
on the same classpath due to the change in package names and Maven
module coordinates.

Download - 
Release notes - <
https://www.apache.org/dist/httpcomponents/httpclient/RELEASE_NOTES-5.0.x.txt



--
This message was sent by Atlassian Jira
(v8.3.4#803005)