|
Mike, You should be okay PTF level wise. I'm pretty sure URL rewriting was working properly prior to V5R2 being released. Does the path /www/logs exist? I don't think that the server will create it automatically. Also, if you have several server instances running, you probably want to change the path to logs/rewrite.log so it goes in the log directory for that instance. Also, how well do you understand regular expressions? You can find several tutorials here: http://www.google.com/search?hl=en&q=regex+tutorial and the book "Professional Apache 2.0" also has a tutorial in it. Finally, here's an example I use to do the opposite of what you want to accomplish: RewriteEngine On RewriteLog logs/rewrite.log RewriteLogLevel 0 RewriteCond %{HTTP_HOST} !consumersplus\.thomsonlearning\.com RewriteRule ^(.*)$ http://%{HTTP_HOST}$1 [R=permanent] If you change the last line to: RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [R=permanent] it should do what you want. What it's doing is when the host name doesn't match consumersplus.thomsonlearning.com, it's redirecting to the non-SSL version of the URL. Since you should never get that host name on your server, changing the last line should do exactly what you want. Also, you'll want to make sure that you either have two server instances running (one on port 80 and the other on port 443) or have virtual hosts (see http://httpd.apache.org/docs-2.0/vhosts/name-based.html) set up (one on port 80, the other on 443) so you don't get into a redirection loop. Matt -----Original Message----- From: Mike Wills [mailto:koldark@xxxxxxxxx] Sent: Wednesday, January 05, 2005 10:53 AM To: Web Enabling the AS400 / iSeries Subject: Re: [WEB400] Apache and .htaccess No, there is not. On Wed, 5 Jan 2005 00:38:42 -0000, Colin Williams <colin.williams@xxxxxxxxxxxx> wrote: > did the rewrite log get created? > > ----- Original Message ----- > From: "Mike Wills" <koldark@xxxxxxxxx> > To: "Web Enabling the AS400 / iSeries" <web400@xxxxxxxxxxxx> > Sent: Tuesday, January 04, 2005 10:15 PM > Subject: Re: [WEB400] Apache and .htaccess > > > I am on V5R2 I am not 100% sure what PTF level we are on. > > > > > > On Tue, 4 Jan 2005 21:14:03 -0000, Colin Williams > > <colin.williams@xxxxxxxxxxxx> wrote: > > > Mike > > > > > > What version of apache / os are you running? > > > > > > RewriteEngine On should switch on mod_rewrite > > > > > > and you should be able to see the results in the rewrite log > > > > > > cheers > > > Colin.W > > > > > > http://as400blog.blogspot.com > > > > > > ----- Original Message ----- > > > From: "Mike Wills" <koldark@xxxxxxxxx> > > > To: "Web Enabling the AS400 / iSeries" <web400@xxxxxxxxxxxx> > > > Sent: Tuesday, January 04, 2005 7:33 PM > > > Subject: Re: [WEB400] Apache and .htaccess > > > > > > > On Tue, 4 Jan 2005 16:29:43 -0000, Colin Williams > > > > <colin.williams@xxxxxxxxxxxx> wrote: > > > > > Mike, > > > > > > > > > > Try url rewriting > > > > > > > > > > RewriteEngine On > > > > > RewriteLog /wwww/logs/rewrite.log > > > > > RewriteLogLevel 9 > > > > > RewriteCond %{HTTPS} !=on > > > > > RewriteCond %{HTTP_HOST} ^mysite.com* > > > > > RewriteRule ^/* https://%{HTTP_HOST}$1 [R,L] > > > > > > > > > > Im not sure if that's exactly right, you may have to play with it to > > > fine > > > > > tune it > > > > > > > > > > The documentation for url rewriting is at > > > > > http://httpd.apache.org/docs/misc/rewriteguide.html > > > > > > > > > > I believe these can also be added to the .htaccess file but ive not > > > tried it > > > > > that way myself > > > > > > > > > > cheers > > > > > Colin.W > > > > > > > > I will have to do some more looking. That didn't work either. How > > > > would mod_rewrite get enabled on apache on iSeries? > > > > > > > > -- > > > > Mike Wills > > > > Midrange Programmer/Lawson Administrator > > > > koldark@xxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.