I didn't. I put it outside the dir directive. I tried moving it back to the
.htaccess file, and it works fine. This should be the same as putting it
inside the dir directive.
But I am still confused about why it is different when it's in the main
conf. I guess I just need to look at the logs to se
In the .conf file are you putting the rules inside a
directive? As far as I know, works the
same as .htaccess, and you should try copying it exactly.
On Feb 19, 2008 4:04 PM, Cliff Hirsch <[EMAIL PROTECTED]> wrote:
>
> I use the following to help work with SEO-friendly URLs:
>
> RewriteBase /
I use the following to help work with SEO-friendly URLs:
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php [L,QSA]
This works fine on my development machine in the main .htaccess file.
On the production machine, I do the same thing
The most direct answer to my question ended up in my spam folder! Because
subsequent emails referred to Austin's reply, I went hunting for it, and there
it was in spam.
I'm into keeping programming as simple as possible except where a more complex
solution is warranted, and this is workable.
On Feb 18, 2008 11:58 PM, Susan Shemin <[EMAIL PROTECTED]> wrote:
>
> thanks, Mike and Ken
>
> first off, I'm not using a form (so no POST); the link is in an anchor tag.
> I could put a form around it, but that seems to me making a simple link
> complex.
>
The conceptual bit that you may be missi
Ken Robinson wrote:
But, Austin, is correct, you don't need AJAX here.
That's true. There are probably a dozen ways to handle this without
Ajax. One lightweight solution would be to have that onclick handler
make a 1x1 image request (with query args) to a hidden DIV.
__
At 11:58 PM 2/18/2008, Susan Shemin wrote:
thanks, Mike and Ken
first off, I'm not using a form (so no POST); the link is in an
anchor tag. I could put a form around it, but that seems to me
making a simple link complex.
You don't understand. The POST method is defined in the AJAX code you
