Apache rewrites redirecting back to the browser

is there a way to get around this?

[mona]

Hi, there. We're having a problem getting apache rewrites to work on a site. This is way out of my reach. I've got a programmer and the tech department working on it, but they can't figure it out. This is the way it was explained to me:

We are using the apache rewrite module in addition to the Enhydra_director module. The default behavior for the rewrite module is to do internal rewrites – in other words, the pretty url gets converted to the ugly url internally within apache, and the web browser is not made aware of the rewrite. For some reason, when using the Enhydra_director module with it, it always sends a redirect back to the web browser informing them of the change.

If this doesn't explain the problem enough, let me know and I'll get more from the programmer. Thank you.

[Birdman]

Hi there.

This quote may be helpful:

Note: If you are using 'mod_rewrite', then you should make sure that the 'LoadModule rewrite_module ...' directive comes BEFORE the 'LoadModule enhydra_director_module ...' directive if you intend to use 'mod_rewrite' to redirect URLs to Enhydra Director. Also you should use the 'mod_rewrite' '[PT]' tag to force pass-through of redirected URLs.

[enhydra.objectweb.org...]

[jdMorgan]

That's strange. Since the execution order on Apache 1.x is the reverse of the LoadModule load order, I'd expect it to be the other way around -- put enhydra at the beginning, not the end.

Apache 2.x uses an entirely-different mechanism for prioritizing module execution order.

Without confusing this issue too much, I'd say to examine the LoadModule order, and change the relative order of mod_rewrite and enhydra. If that helps, leave it that way, and if not, restore your backup and look elsewhere.

Jim

[mona]

Thanks Birdman and jdMorgan. Hopefully your responses will explain things to the programmer. He's out until Monday, so I won't know until then.