FYI, it was an Backend Issue (as always) and Support provided me with these details about it.
This counts only for the new URL's, the existing URL's cannot be fixed because those are already Re-written by the Sonicwall.
So i reported this issue to the back-end team and they mentioned below information:
"The backend verify the HK not matched, the backend calculate a HK value ‘f8c593af09651950c2b536fa34b5559ea6c87e92296b95c4ad66e308ce0386a0’, not ‘FFD5663242372F265432EBF2850233FC739759944B4FDC187EB5A20AFCF04410’ in the link.
So return a “bad request” page instead of redirect, not caught as malicious.
This issue has been found many times long time ago, we try to use a new protocol to fix it."
So they have used new protocols to fix this false positive issues which are happening frequently these days. Please monitor and let me know the results.
Hopefully this new protocol will avoid future problems.
@BWC thank you for the update. Meanwhile ToC is accepted by the Users. It sometimes was confusing to click on these long modified link terms, but when in the end the page opened all was ok.
A broken Link caused problems because you could not fixed it on the users end and often you can´t get these links again.
Comments
Hello @ThK,
This issue is resolved. Please do let us know if you see further issues. We apologies for the inconvenience caused.
🖐️ Sr. Manager, Web and Digital, SonicWall. Say "hi" by tagging me at @micah.
Hi,
today a on-prem ES customer reported about the same "Bad Request" problem, copy&paste of the original URL worked though.
What causes this and can it be avoided?
--Michael@BWC
Hi,
FYI, it was an Backend Issue (as always) and Support provided me with these details about it.
This counts only for the new URL's, the existing URL's cannot be fixed because those are already Re-written by the Sonicwall.
So i reported this issue to the back-end team and they mentioned below information:
"The backend verify the HK not matched, the backend calculate a HK value ‘f8c593af09651950c2b536fa34b5559ea6c87e92296b95c4ad66e308ce0386a0’, not ‘FFD5663242372F265432EBF2850233FC739759944B4FDC187EB5A20AFCF04410’ in the link.
So return a “bad request” page instead of redirect, not caught as malicious.
This issue has been found many times long time ago, we try to use a new protocol to fix it."
So they have used new protocols to fix this false positive issues which are happening frequently these days. Please monitor and let me know the results.
Hopefully this new protocol will avoid future problems.
--Michael@BWC
@BWC thank you for the update. Meanwhile ToC is accepted by the Users. It sometimes was confusing to click on these long modified link terms, but when in the end the page opened all was ok.
A broken Link caused problems because you could not fixed it on the users end and often you can´t get these links again.
-Thomas