|
Group: Forum Members
Last Active: Tue 23 Feb 2021
Posts: 18,
Visits: 88
|
Hello
We've recently started using Request Filtering in IIS rather than URLScan. Previously I was able to exclude any Kartris sites from using URLScan simply by deleting URLScan from the list of ISAPI filters.
Can't do this with Request Filtering, and have found that Kartris sites don't work properly now with Request Filtering rules in place.
The main issue is the accordion navigation menu won't expand, and tabbed content on product pages won't display.
Does anybody have any ideas please as to which specific settings in Request Filtering will be blocking this?
Thanks,
Simon
|
|
Group: Administrators
Last Active: Tue 10 Sep 2024
Posts: 807,
Visits: 2,748
|
Request filtering is on by default in most cases for anything other than (very old) IIS6 installs, and we don't see problems with it, apart from a few isolated cases. Generally the issues are with older CactuShop URLs that may include ampersands within the friendly URL e.g. /bits-&-bobs/. Kartris won't format URLs like that, but CactuShop did and so incoming links often trigger the request filtering.
It sounds more like something in your custom rules? It sounds like parts of the page formatted with scripts or the ajaxtoolkit are not working. What rules do you have in place?
--
If my post solves your issue, can you 'Mark as Answer' so it's easier for other users to find in future.
If you would like to be informed of new features, new releases, developments and occasional special bonuses, please sign up to our mailing list: http://bit.ly/19sKMZb
|
|
Group: Forum Members
Last Active: Tue 23 Feb 2021
Posts: 18,
Visits: 88
|
Thanks for the reply Paul
I think I have it sorted now, the two offending rules were:
1, . in querystring - I was allowing this with an always allow rule for /Image.aspx - but it turns out this needed allowing
2, querystring lengths, I had set these to be quite restrictive, increasing to 500 worked
Thanks,
Simon
|