Forum Discussion
Handling dynamic pseudoparameters in ASM policies
Hi folks, I have a challenging typo3 web application regarding ASM: I want to enforce parameters but unfortunately this application uses pseudo parameters for identifying (un)changed files.
A typical request looks like this: GET /typo3conf/ext/sitecore/Common/Public/JavaScript/foundation/foundation.forms.js?137162555
The pseudo parameter is a unix-timestamp.
Can anyone tell me how to configure the ASM to ignore this parameter? Adding a wildcard parameter () on URL level (/typo3conf/ext/sitecore/Common/Public/) doesnt help unfortunately...
Cheers
4 Replies
- rob_carr
Cirrocumulus
Have you tried setting up a no-name type parameter with a wildcard (or possibly a regex expression) on the URL? - Did you ever get anywhere with this? I've got the same problem.
- willerman
Nimbostratus
No, unfortunately not :( it looks like a path parameter you might be able to do something with that, look at the profile, advanced settings: Handle Path Parameters
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
