Re: [users@httpd] Cookies and Apache 2

2005-07-09 Thread Aman Raheja
Hi Peter To get a better idea of what is happening, you can probably put a sniffer and see what is being sent to the broweser, I mean the header - so that you can look at the cookie being set. It won't happen that you click on refresh 3-4 times and apache will change it's behaviour - to me thi

[users@httpd] mod_rewrite, RewriteBase, and .htaccess?

2005-07-09 Thread Jay Levitt
I'm trying to set up a server with Apache 2.0.54 and Ruby on Rails, such that I can create a directory /srv/www/rails/xxx and have xxx.rails.jay.fm launch the appropriate Rails app, without manually creating the VirtualHost. Rails uses .htaccess to rewrite URLs. If I had test.rails.jay.fm set

[users@httpd] Cookies and Apache 2

2005-07-09 Thread Peter Gourlie
Hi all,   I'm relatively new to this, and to be honest I don't quite understand how Apache works completely, but I have searched the internet as well as the FAQ for any information on the various cookie settings and Apache 2.    To be more specific, I am using a web portal, php-nuke (www.phpnuke.

Re: [users@httpd] Quite consistent SEG FAULT because of logrotate (apache 2.0.54)

2005-07-09 Thread James A
I dont use any external modules. Here is my apache compile script (see below). I only use it with PHP, 4.3.11, upgraded from 4.3.4 because same problem. Do you recall any good stable PHP version? #!/bin/sh ./configure --enable-layout=RedHat \ --enable-access \ --enable-actions \ --enable-alias

Re: [users@httpd] Quite consistent SEG FAULT because of logrotate (apache 2.0.54)

2005-07-09 Thread Nick Kew
James A wrote: > Is this known bug? No. That kind of thing is usually caused by buggy third-party modules. What happens if you remove them? > Because I read here : Follow that to the bugs database http://issues.apache.org/bugzilla/show_bug.cgi?id=10164 and it's PHP, not Apache. -- Nick kew

[users@httpd] Odd interaction between mod-rewrite and mod-cgi

2005-07-09 Thread Sean Conner
I have a few CGI scripts, written in C (legacy stuff that I don't wish to rewrite if possible) that work fine under Apache 1.3. When moved to Apache 2.0.54 (latest version) they still work, but Apache seems to include additional output at the bottom of the page: HTTP/1.1 200 OK Date: S