Dispatcher mod_rewrite not working? | Community
Skip to main content
daitienshi
daitienshi
New Participant
August 23, 2017
Solved

Dispatcher mod_rewrite not working?

  • August 23, 2017
  • 12 replies
  • 5860 views

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!

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by joerghoh

    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

    12 replies

    D
    dorianhallward
    New Participant
    January 18, 2018

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

    D
    dorianhallward
    New Participant
    January 17, 2018

    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?

    daitienshi
    daitienshiAuthor
    New Participant
    January 17, 2018

    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.

    D
    dorianhallward
    New Participant
    January 17, 2018

    daitienshi, @Jorg Did this get resolved? I'm seeing similar.

    daitienshi
    daitienshiAuthor
    New Participant
    August 23, 2017

    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.

    joerghoh
    joerghohAccepted solution
    Employee
    August 23, 2017

    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

      daitienshi
      daitienshiAuthor
      New Participant
      August 23, 2017

      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!

      joerghoh
      joerghoh
      Employee
      August 23, 2017

      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)

        daitienshi
        daitienshiAuthor
        New Participant
        August 23, 2017

        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

        joerghoh
        joerghoh
        Employee
        August 23, 2017

        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

        Show more replies
        Terms & ConditionsAccessibility statement

        Loading footer...