Forum Discussion
ASM Proactive Bot - Referer Header
Hi All,
I turned on ASM Proactive Bot detection and our analytics folks noticed that the Referer Header isn't carried through after the JS challenges are complete.
By the time the client browser answers the JS challenges, it sees the requested URL as the Referer instead of Google (as in our specific case). Analytics would like to see Google as the Referer.
Is there anyway to conserve the original Referer so that the backend sees it as an organic request?
Thanks for any insight you have.
Cheers,
Mike
- Simon_BlakelyEmployee
What version of BigIP are you using?
Try setting the specific target URL to be "qualified"
# tmsh modify sys db asm.cs_qualified_urls value <url>
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