You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in issue #7934, it seems that the router might not recognize paths defined using patterns like those used by @Filters.
I'm afraid that checking for known paths reintroduce the same issue, causing all requests to a proxy filter to be blocked by the CORS filter with a 403 Forbidden error.
Hello!
As mentioned in issue #7934, it seems that the router might not recognize paths defined using patterns like those used by
@Filter
s.I'm afraid that checking for known paths reintroduce the same issue, causing all requests to a proxy filter to be blocked by the CORS filter with a 403 Forbidden error.
This situation seems to prevent us from implementing solutions suggested in the official documentation, such as the one found here: https://docs.micronaut.io/latest/guide/#proxyClient
Here's a snippet of the code in question:
Originally posted by @ThomasIommi in #11097 (comment)
The text was updated successfully, but these errors were encountered: