You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have been trying to intercept an http request that triggers a specific batch.js file which is causing us delay. For this we are using servlet filters.
But here is the interesting part: The filter is being written for the url-pattern
but it is not capturing all the requests associated with this pattern.
The one request we want to capture has some CDN ids and other unique ids appended just after the base url. Instead of capturing that request itself, what is happening is that somehow a new request with similar path is getting generated and the servlet filter operations are being performed on that request. The new almost duplicate request that is being generated is missing all those CDN ids and unique numbers from the url, rest of it is same.
We would really appreciate if someone can explain what is happening, how we are getting this almost duplicate request and how we can ensure that the original url is captured.
PS: We have tried to give complete url path in url-pattern but that did not work. At that time even no new url was getting created.