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 ...
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 ei...
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
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.
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
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?
- 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 ...