MOD_REWRITE Question

[bostonmacosx]

So here is my dilemma.

http://server/twit/pages/confirm.php?email=[e-mail]&confirm_code=12345

works great and I get the email I expect

with the REWRITE

RewriteEngine On
RewriteRule ^confirm/(.*)/(.*)$ confirm.php?email=$1&confirm_code=$2 [L]

when I sent it

http://server/twit/pages/confirm/[e-mail]/12345

I acutally get 5 emails from the page...

The Correct Email is

There was a problem with the registration of EMAIL: [e-mail] with confirm code of 12345

The incorrect with the mod rewrite I get 5 separate emails

There was a problem with the registration of EMAIL: [e-mail] with confirm code of 12345

There was a problem with the registration of EMAIL: functions/js with confirm code of prototype.js

There was a problem with the registration of EMAIL: css with confirm code of main.css

There was a problem with the registration of EMAIL: functions/js with confirm code of main_site.js

the body of the email which is in a loop is

$mymail -> Body = "There was a problem with the registration of EMAIL: $_GET[email] with confirm code of $_GET[confirm_code]";

so somehow there are multiple GET[email] and GET[confirm_codes] going into the loop.

I have no idea why this is happening it apears that the mod_rewrite is correct.
Any help appreciated.

[Derokorian]

Actually what's happening is the browser is making separate requests for your js and css files, which are being rewritten to your script. You should use RewriteCond to check that they aren't requesting an actual file. http://httpd.apache.org/docs/current/mod/mod_rewrite.html

[bradgrafelman]

Another problem I see is that this:

http://server/twit/pages/confirm/[e-mail]/12345

or rather, the "path" portion of that URL:

twit/pages/confirm/[e-mail]/12345

will not match your RewriteRule since it doesn't begin with "confirm" (as your RewriteRule requires).

EDIT: This is, of course, assuming your .htaccess file is placed in the root of your site and no RewriteBase directive is used.

[bostonmacosx]

Derokorian;11000395 wrote:

Actually what's happening is the browser is making separate requests for your js and css files, which are being rewritten to your script. You should use RewriteCond to check that they aren't requesting an actual file. http://httpd.apache.org/docs/current/mod/mod_rewrite.html

I'm sorry I don't really understand the RewriteCond...could you explain it a bit possibly.

here are two of the includes in the document.

<script type="text/javascript" src="../functions/js/prototype.js"></script>
    <script type="text/javascript" src="../functions/js/main_site.js"></script>

[Ashley_Sheridan]

The rewrite isn't something that is part of PHP, rather it is part of Apache, your web server.

Now when you visit a website with a browser, it first makes the request to grab the pages HTML. Then, as you receive that, your browser sees that it needs to grab various images, CSS and javascript files, so it asks the server for each one of those too.

The server is getting multiple requests from your browser, and each one of those requests is being re-written by Apache because of the rule you have in your .htaccess file. As Derokorian mentioned, you should add in a check to make sure that it's only re-writing requests for files that don't exist, or narrow down your .htaccess regular expression a little more so that it isn't just matching any old string.

[bostonmacosx]

Ashley Sheridan;11000427 wrote:

The rewrite isn't something that is part of PHP, rather it is part of Apache, your web server.

Now when you visit a website with a browser, it first makes the request to grab the pages HTML. Then, as you receive that, your browser sees that it needs to grab various images, CSS and javascript files, so it asks the server for each one of those too.

The server is getting multiple requests from your browser, and each one of those requests is being re-written by Apache because of the rule you have in your .htaccess file. As Derokorian mentioned, you should add in a check to make sure that it's only re-writing requests for files that don't exist, or narrow down your .htaccess regular expression a little more so that it isn't just matching any old string.

I undersand that however I just don't understand how to make this happen because my .htaccess file is in the /pages/ folder and the JS And CSS files are in different folders...so how do I prevent the rewrite for the INCLUDED files.

Rob

[Derokorian]

use the actual url instead of a relative. What a relative does is make a request for this folder, then go up a folder then go to the js file, as opposed to make a request for the file directly such that the pages folder is never involved.

[bostonmacosx]

There has to be a better way using RewriteCond because I work on this site on two servers....so if I had to hard code the absolute regeference to each of the include files I'd break one of the sites consistently..

Suggestions?

[bradgrafelman]

bostonmacosx;11000447 wrote:

There has to be a better way using RewriteCond

There is:

Derokorian;11000395 wrote:

You should use RewriteCond to check that they aren't requesting an actual file. http://httpd.apache.org/docs/current/mod/mod_rewrite.html

For example, you might do:

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
[I]<Your RewriteRule here>[/I]

to make a given RewriteRule only apply if the requested URL doesn't map to an actual file or folder on the filesystem.

[sneakyimp]

I've seen an approach to this that might be a little more easy to do. You'd create one rewrite rule that matches all of these things that are supposed to send you an email:

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^confirm/ your_file.php [L]

where the [L] tells apache to stop checking after that particular rule matches

Then, within your_file.php, you could take a peek at $SERVER['REQUEST_URI'] and use PHP's much more friendly functions to parse the results:

$args = explode("/", $_SERVER["REQUEST_URI"]);
print_r($args); // check out the elements in this array 

[bradgrafelman]

@: You could even go a step further and just redirect all requests to a master PHP file that does any needed redirecting and whatnot. It'd be less efficient, harder to debug, potentially confusing for others, but... well you could.

... or you could just learn how to use mod_rewrite properly. :p

[bostonmacosx]

Unfortunately this is still rewriting incorrectly

RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^confirm/(.*)/(.*)$ confirm.php?email=$1&confirm_code=$2 [L]

http://server/pages/confirm/test/test/
SO it is trying to get the included CSS file at
pages/confirm/test/css/main.css
should be
ARRRGGGHHHH.....why?
I can't use absolute links for the included files.

So the includes stated above are firing off the follow emails.
You have received an email from: txt/javascript with the confirm code: prototype.js

[bradgrafelman]

bostonmacosx;11000948 wrote:

http://server/pages/confirm/test/test/
SO it is trying to get the included CSS file at
pages/confirm/test/css/main.css

What is the path you're using for the CSS file? If it's "../css/main.css" then that path makes sense.