Restricting Query Strings in dispatcher.any not working | Community
Skip to main content
25793466
Level 2
Jul 24, 2018 3:12 PM UTC
Solved

Restricting Query Strings in dispatcher.any not working

I want to disable any URL with query strings but allow those that don't.  The "Note:" section of Configuring Dispatcher says the following should work:

/0001 { /type "deny" /method "*" /url "/mysite/content/test/*" }

/0002 { /type "allow" /method "GET" /url "/mysite/content/test/*" }

/0003 { /type "deny" /method "GET" /url "/mysite/content/test/*" /query "*" }

When I try https://my.site.com/mysite/content/test/home.html, it is getting blocked /0003

It should work, given "If a rule contains a /query, it will only match requests that contain a query string and match the provided query pattern."

For testing purposes my /filter section only contains those 3 rules.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
25793466Accepted solution
Level 2
Oct 10, 2018 7:11 PM UTC

It turns out there is an issue with the dispatcher version we are using.  I don't know if it effects all platforms, but it is not working correctly on 4.2.0 on IIS, x64 non-ssl version.

I tested the same exact dispatcher configuration (dispatcher.any) on the latest dispatcher (v4.2.3) and the filter rules are working correctly with query strings.

View reply

7 replies

25793466AuthorAccepted solution
Level 2
Oct 10, 2018 7:11 PM UTC

It turns out there is an issue with the dispatcher version we are using.  I don't know if it effects all platforms, but it is not working correctly on 4.2.0 on IIS, x64 non-ssl version.

I tested the same exact dispatcher configuration (dispatcher.any) on the latest dispatcher (v4.2.3) and the filter rules are working correctly with query strings.

Translate
praneethm583275
New Participant
Sep 6, 2018 5:59 PM UTC

Hi nivedtha,

I am having some doubts regarding the AEM can you please help me out

[Personal contact info removed]

Translate
Nisha_Nivedita
Nisha_Nivedita
Employee
Sep 6, 2018 5:50 PM UTC

/0029 { /type "allow" /method "GET" /url "/content/geometrixx-outdoors.html" }

/0030 { /type "deny" /method "GET" /url "/content/geometrixx-outdoors.html" /query "*" }

Above should work, however content might be getting served from cache regardless of query string attached or not

Translate
25793466Author
Level 2
Jul 25, 2018 5:16 PM UTC

That didn't work.  We run AEM within an application server and it's not possible to run at the root.  (We even had ACS unseccuessufully attempt to change that).  All of our /filter rules are prefixed with /mysite and we haven't had any issues since we launched the site over two years ago.

I added a fourth rule to test your suggestion.

/0004 { /type "allow" /method "GET" /url "/content/test/*" /query "a=*" }

https://my.site.com/mysite/content/test/home.html?a=test does not work.  It does work when rule 4 is:

/0004 { /type "allow" /method "GET" /url "/mysite/content/test/*" /query "a=*" }

Translate
GaneshM
GaneshM
Level 3
Jul 25, 2018 5:01 AM UTC

Hi,

Could you please remove the "mysite" from path and try?, you need to define only AEM path which is like /content/ , /apps/ , /etc/.

Eg :

/0001 { /type "deny" /method "*" /url "/content/test/*" }

/0002 { /type "allow" /method "GET" /url "/content/test/*" }

/0003 { /type "deny" /method "GET" /url "/content/test/*" /query "*" }

Wondering why your sample dispatcher URL looks /mysite/content/test/home.html , the best practice is always starts with /content/ like mysite.com/content/test

Thanks!

Translate
25793466Author
Level 2
Jul 24, 2018 6:46 PM UTC

I should have mentioned that.  We are using 4.2.0 on IIS.  x64 non-ssl version.

Translate
vish.dhaliwal
Employee
Jul 24, 2018 6:22 PM UTC

Hello,

Make sure you have dispatcher version 4.1.5 or greater than 4.1.5.

Regards,

Vishu

Translate
Terms & ConditionsAccessibility statement

Loading footer...