daitienshi

Changes in local publisher CRX not reflecting on the site - Adobe Experience Manager 07-06-2018

Hi,I've noticed that changes to a jsp or css in my local publisher's CRX are not showing up on the site after saving. I'm viewing the pages directly against the publisher instance without a dispatcher.The only time the changes seem to be reflected is when I make changes in my IDE and I re-build and deploy the package to AEM. This makes it very cumbersome for minor tweaks to the page to have to re-build everything.I recently upgraded to 6.2 with the SP2 and CFP. It was all working prior to the SP...

461

Re: Dispatcher mod_rewrite not working? - Adobe Experience Manager 17-01-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.

973

Re: Dispatcher mod_rewrite not working? - Adobe Experience Manager 23-08-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.

924

Re: Dispatcher mod_rewrite not working? - Adobe Experience Manager 23-08-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!

928

Re: Dispatcher mod_rewrite not working? - Adobe Experience Manager 23-08-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

926

Re: Dispatcher mod_rewrite not working? - Adobe Experience Manager 23-08-2017

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!

932

Dispatcher mod_rewrite not working? - Adobe Experience Manager 23-08-2017

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 combin...

3.4K

Re: AEM Dispatcher not resolving vanity urls - Adobe Experience Manager 23-08-2017

I believe this is now fixed. It turns out the documentation on the dispatch configuration (Configuring Dispatcher - docs.adobe.com ) has a typo in the first example configuration, where it lists the entry as "/vanity-urls". However, later on in the vanity urls section (https://docs.adobe.com/content/docs/en/dispatcher/disp-config.html#Enabling Access to Vanity URLs - /vanity_urls), it's listed as "/vanity_urls". The proper configuration is indeed with the underscore and not the hyphen (i.e. /van...

1.3K

Re: AEM Dispatcher not resolving vanity urls - Adobe Experience Manager 22-08-2017

Looking at the dispatcher log, I'm seeing that the vanity-urls entry in the dispatcher.any file is not being recognized.That would explain why it's not making the call to the publisher. Any reason you can think of as to why this warning is showing?

1.3K

Re: AEM Dispatcher not resolving vanity urls - Adobe Experience Manager 22-08-2017

- I'm able to access the vanity urls if I bypass the dispatcher and go straight to the Publisher. I know it has something to do with the webserver config but just trying to see what it could be.- how would I switch off the mod_rewrite to do the quick test? Based on the dispatcher log, it seems like it's trying to go to my vanity url (/home) even after the filter, so it seems like it's checking the vanity urls file. However, like I said, the access.log on the publisher never shows the dispatcher ...

1.3K

Likes from

User

Count

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe