[jira] [Commented] (CAMEL-22080) Http component oauth2 cache based on the full endpoint URI

["Mikael Andersson Wigander (Jira)" <ji...@apache.org>]

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

Mikael Andersson Wigander commented on CAMEL-22080:
---------------------------------------------------

Further tests concludes it even considers query parameters as part of the URI making them unique.

[https://localhost/event?eventId=1]

[https://localhost/event?eventId=2]

Same issue here, they are cached but they both request a new token

> Http component oauth2 cache based on the full endpoint URI
> ----------------------------------------------------------
>
>                 Key: CAMEL-22080
>                 URL: https://issues.apache.org/jira/browse/CAMEL-22080
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-http
>            Reporter: Mikael Andersson Wigander
>            Priority: Minor
>
> In the http component there's a setting to cache the token, .oauth2CacheTokens(true).
> This cache is using the complete URI including dynamic parts which makes it request a new token when the path changes.
> [https://localhost/event/1]
> [https://localhost/event/2]
> Both above are cached so a subsequent call to any of these will be using the cache but the initial call will call the oauth2TokenEndpoint URI for both of them and request a new token.
>  



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