Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Dispatcher mod_rewrite not working?

Avatar

Level 2

Related to another post (AEM Dispatcher not resolving vanity urls),​ I've created some rewrite rules in my httpd.conf in my dispatcher so that when I hit my site's root (e.g. www.mysite.com/), it should rewrite/redirect to a page of my choosing (e.g. www.mysite.com/content/mysite/login.html).

However, when I hit the root, I'm getting a response with a redirect (302) to /index.html instead, even though I've created a rewrite rule for this.

In my httpd.conf, I have:

Ideally, what I'd like is a combination of vanity urls and rewrite so that anything that hits the root get redirected to the vanity url, which I had tried to set up by configuring the sling:redirect property of the /content node, but the dispatcher keeps returning index.html instead of the value of the sling:redirect.

Thanks!

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

In the second case the dispatcher still forwards the request to AEM, although it should not. Have you restarted the httpd to make that change effective?

If yes, please provide all webserver configuration (including dispatcher config) for both cases and report an issue with AEM support.

Jörg

View solution in original post

0 Replies

Avatar

Employee Advisor

Have you set in the httpd.conf the statement "DispatcherDeclineRoot 1"?

See Installing Dispatcher - docs.adobe.com

regards,

Jörg

Avatar

Level 2

Hi,

I did set that value to 1 and the dispatcher.log still says it's returning a 302 to /index.html. 

Is this supposed to let the root request pass through to the publisher? This way the publisher can return the redirected page as configured in the sling:redirect in the /content node?

Thanks!

Avatar

Employee Advisor

If you want to handle the initial redirect on the apache webserver, set it "1"; if you want to handle the redirect on hitting "/" on the AEM publish, set it to "0".

Jörg

Avatar

Level 2

I've set it to 0 so the publisher can return the right page back, but I'm still seeing an index.html being returned to the dispatcher and the publisher's request log doesn't seem to show the request for the page.

When setting it to 1 and having those rewrite rules on, it doesn't seem to be working either as it comes back with index.html instead of the login.html

Avatar

Employee Advisor

Can you set the dispatcher loglevel to DEBUG and post the relevant log snippets then?

("If you don't find the log statements you are expecting in the log, you are looking at the wrong log". -- Old debugging wisdom, author unknown)

Avatar

Level 2

I've actually set it to TRACE just but here's the log snippet for when the DispatcherDeclineRoot is set to 0:

Here is the log snippet when I set the DispatcherDeclineRoot to 1:

Thanks!

Avatar

Correct answer by
Employee Advisor

In the second case the dispatcher still forwards the request to AEM, although it should not. Have you restarted the httpd to make that change effective?

If yes, please provide all webserver configuration (including dispatcher config) for both cases and report an issue with AEM support.

Jörg

Avatar

Level 2

Thanks. Yes, between switching the values, I've restarted apache. 

I'll open up a ticket with AEM support and provide all of the configurations there.

Avatar

Level 2

Yep. Turns out because the site is using SSL, I had to put the rewrite rules in our ssl.conf file that contained the virtualhost entry for the secured site.  Once that's in there, it worked.

Avatar

Level 4

Thanks daitienshi​,

I added a sling internal redirect, to handle request matching e.g. localhost.4503/$.  While the mapping worked ok when accessing the publish instance directly, i.e. http://localhost:4503 internally redirects as i'd hope to, when accessing via apache/dispatcher the dispatcher logs out a 302 http response and subsequently tries to GET /index.html.

I have a dispatcher.any allow filter - i imagine similar to what you were trying - such as

and I'm not using SSL.

I'm struggling to understand what returns the 302 when requesting the '/' resource?  Is there simply no mapping and redirect to cater for the request from apache/dispatcher (i.e. will localhost.4503 only serve requests that are made directly to the publisher with the port included?)?

I'm sure this is simple! Any guidance appreciated?

Avatar

Level 4

Answering my own question(s), index.html returned when '/' not matched by any etc/map rules and root mapping servlet handles the request.