Nslookup text in post causes a 403?
Discussion
Copying this over from another thread – but essentially what you're posting is deemed as malicious. Appreciate you're trying to be helpful though!
afrere_ph said:
As you've gathered these types of issues do pop up rarely for certain inputs as the firewall we run (to keep the forums secure) can sometimes falsely interpret safe text as malicious. We do plan at some point to make this experience better, but for now it is a known limitation for a small percentage of posts.
That said, you can use the Preview function to gradually isolate the problematic bit in the block of text - e.g. for the text block, start with just the first paragraph and try Preview, if you see 403 you know the bad part exists within there and can go back and further filter it down.
It is a fiddly process, but given the firewall is a managed service and uses an industry standard ruleset to catch security risks, there isn't much else that can be done at the moment (without significant dev effort!).
Alternatively, feel free to post a screenshot of the text that's being blocked, or email info@pistonheads.com and we may be able to shed some light.
Cheers!
That said, you can use the Preview function to gradually isolate the problematic bit in the block of text - e.g. for the text block, start with just the first paragraph and try Preview, if you see 403 you know the bad part exists within there and can go back and further filter it down.
It is a fiddly process, but given the firewall is a managed service and uses an industry standard ruleset to catch security risks, there isn't much else that can be done at the moment (without significant dev effort!).
Alternatively, feel free to post a screenshot of the text that's being blocked, or email info@pistonheads.com and we may be able to shed some light.
Cheers!
Gassing Station | Website Feedback | Top of Page | What's New | My Stuff


