Home/ Questions/Q 47885
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T16:11:34+00:00

I’m pulling my hair out on what should be an insanely simple problem. We

  • 0

I’m pulling my hair out on what should be an insanely simple problem. We are running WebSphere IHS (Apache) through an F5 BigIP. BigIP is doing the https translation for us. Our url (changed for web, not valid) is https://superniftyserver.com/lawson/portal.

When someone types in just that without the slash after portal, Apache assumes ‘portal’ to be a file and not a directory. When Apache finds out what it is, it sends the 301 Permanent Redirect. But since Apache knows only http, it sends the URL as http://superniftyserver.com/lawson/portal/ which then creates problems.

So I tried a server level httpd.conf change for mod_rewrite, this is one of the dozens of combinations I’ve tried.

RewriteEngine on RewriteRule ^/lawson/portal(.*) /lawson/portal/$1

I also tried RewriteRule ^/lawson/portal$ /lawson/portal/

Among many other things… What am I missing?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. If you can’t get an answer on the RewriteRule syntax, here are two other options for you: Write an custom iRule on BigIp (see F5 DevCentral) that looks for 301 responses and convert them to SSL; let the URL pass into your WebSphere server and do a programmatic redirect that sends out HTTPS. However, because F5 terminates the SSL connection, you have to set a custom header that you configure (see PQ86347) so the Java request.getScheme() works as you would expect.

    • 0