RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^/(.*) https://ourserver.com/$1 [L,R,NE]
This seems to work for requests purely at the web server level, but when trying for any WebSphere app, it doesn't forward. I guess maybe it gives the request to the app server before checking the rewrite condition?
What's the best way to do this? We're running WebSphere 7.0 on linux, if it makes a difference.
Thanks very much,
Dan
{code}
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^/(.*) https://ourserver.com/$1 [L,R,NE]
{code}
I wasn't thinking about the format tags on the forum.
If this is in virtualhost context, it should work.
If it's in <Directory> or some htaccess, it will never be evaluated
because websphere will have mapped it to something that's not a
directory / not in the filesystem.
Not covered in the general FAQ for mod_rewrite + plugin here, but maybe
some more tidbits that will help:
http://publib.boulder.ibm.com/httpserv/ihsdiag/plugin_alter_uri.html
--
Eric Covener
This one sounds strange to me, rewrite rules we create in the httpd.conf are handled for the
WAS server as well as for the IHS server.
Maybe it's the placement of the WebSpherePluginConfig "C:\IBM\HTTPServer\Plugins\config\webserver1\plugin-cfg.xml"
directive?
Try to place this one above the rewrite rules in your httpd.conf?
Regards,
Marco
Not a consideration between the interaction of these two modules.
--
Eric Covener