Posted by Saba Ansari on July 7, 2010
actually I just put the directive into the httpd.conf file and i see that the log file is being created upon restart of apache.
But when I invokde the rewrite nothing gets logged into it.
Any guidance is greatly appreciated.
Please excuse my ignorance I went though that link but I still don’t understand how it needs to be defined.
Do I have to put it in httpd.conf? Could you please give me an example?
Posted by Saba Ansari on July 7, 2010
Please excuse my ignorance I went though that link but I still don’t understand how it needs to be defined.
Do I have to put it in httpd.conf? Could you please give me an example?
Posted by Saba Ansari on July 6, 2010
I added the the RewriteLog entry but no matter which location i specify I get the following error:
“C:/Program Files/Apache Software Foundation/Apache2.2/scripts/.htaccess: RewriteLog not allowed here”
What am I missing here?
Posted by Saba Ansari on July 3, 2010
On 03.07.2010 14:08, Rainer Jung wrote:
I made the VAL argument in ENV=VAR:VAL optional for httpd trunk:
http://svn.apache.org/viewvc?rev=960233&view=rev
and proposed it for backport to httpd 2.2.x. It’s a trivial change, no risk, and a nice shortcut for configuration. Otherwise the module should at least complain about an invalid flag syntax.
Nice cross project interaction
Regards,
Rainer
Posted by Saba Ansari on July 3, 2010
On 02.07.2010 22:02, Christopher Schultz wrote:
Right, I’d say it’s a buglet in mod_rewrite. Maybe something I can improve for httpd trunk … (I need to check whether it still behaves the same there).
Regards,
Rainer
Posted by Saba Ansari on July 1, 2010
Rainer Jung wrote: Hi. I usually find helpful the Apache httpd request processing cycle diagram found here : http://perl.apache.org/docs/2.0/user/handlers/http.html That page is part of the mod_perl documentation, explaining how the Apache/perl integration works. But since mod_perl digs deep inside Apache httpd, the various stages of request processing by mod_perl follow the internal Apache httpd cycle very closely. For example, it helps in figuring out at what stage and in what order things like mod_rewrite, JkMount, , content handlers etc.. play a role, how they combine, and at which level you can intervene to do what. It must exist somewhere, but I have not yet found an original Apache httpd document which explains these things so well. Forget the perl-specific stuff that you find there, just follow the explanations and the links. It is really a good tutorial into the insides of Apache httpd’s request processing.
Posted by Saba Ansari on June 4, 2010
On Fri, Jun 4, 2010 at 9:48 AM, Alex Harvey wrote:
Shouldn’t this one be easy to test?
Posted by Saba Ansari on May 31, 2010
Hi,
I had the same problem with mod_auth_kerb.
My solution was to change the RewriteRule to: RewriteRule .* – [E=RU:%1,NS]
From Apache documentation: ‘nosubreq|NS’ (used only if no internal sub-request) This flag forces the rewriting engine to skip a rewriting rule if the current request is an internal sub-request
%{LA-U:REMOTE_USER} is doing such an internal sub-request. And with the NS-flag it isn’t be rewritten to it self again and again…
By,
Martin Koerner
Posted by Saba Ansari on May 30, 2010
Use the proxy flag P in the redirect to preserve the url but have in mind that it will work for the first page only. When you click on any link on it the url will be changed to the new one then.
Sent from my phone
On May 30, 2010 5:20 AM, “Mari Masuda” wrote:
Hello,
I am moving a large website from a proprietary CMS to Drupal. In the proprietary CMS, all media files (images, pdfs, etc.) have URLs like http://media.xxx.org/images/blah.jpg or http://media.xxx.org/documents/blah.pdf. In my Drupal .htaccess I have created the following two mod_rewrite rules so that the old URLs will continue to work and so we can continue using the scheme of http://media.xxx.org/images/whatever.jpg instead of using the Drupal location:
Posted by Saba Ansari on May 29, 2010
Hello,
I am moving a large website from a proprietary CMS to Drupal. In the proprietary CMS, all media files (images, pdfs, etc.) have URLs like http://media.xxx.org/images/blah.jpg or http://media.xxx.org/documents/blah.pdf. In my Drupal .htaccess I have created the following two mod_rewrite rules so that the old URLs will continue to work and so we can continue using the scheme of http://media.xxx.org/images/whatever.jpg instead of using the Drupal location: