And did you set ServerName to include the port. Just "Listen" and "VirtualHost" aren't enough. ServerName is what the rewrite engine uses.
David Am 03.04.2007 um 03:09 schrieb Daniel Swarbrick: > Ok, here is the weirdness. > > On the problematic box, I edit index.php, and add these two lines > at the > top: > > phpinfo(); > die; > > Ok? So no agavi processing will ever get to take place. Now, accessing > that server as https://myhost:9443/index.php correctly shows > SERVER_PORT > as 9443. > > BUT... accessing the server as https://myhost:9443/ (note: missing the > index.php) shows SERVER_PORT as 443. Hmm that's weird, I actually > connected to the server on 9443 :? > > If I rename .htaccess to something else (ie, prevent enabling > mod_rewrite for that vhost), then both those urls above show the > correct > SERVER_PORT 9443. > > So, wouldn't that suggest that it is a mod_rewrite problem > (or .htaccess > rewrite rule problem)? Yes, I know this basically means it's not > agavi's > fault - it's just that the previous "incorrect" method of doing a > redirect actually worked around this problem. > > > Daniel Swarbrick wrote: >> David Zülke wrote: >> >>> It is not a hassle to implement. It never worked for you, you simply >>> didn't notice before as you didn't use <base href /> etc. Fix your >>> rewrites (no idea what's wrong there, typical Apache madness I'd >>> guess), or add a workaround to app/config.php that copies >>> REDIRECT_SERVER_PORT (or whatever it is called) to SERVER_PORT. >> >> I'm using the default .htaccess from the Agavi sample app, and just >> setting the rewrite base to '/' - is there something in that file >> that >> needs fixing? >> >> I don't think I have any "apache madness" on my hands here - I've >> been >> using Apache for about ten years now, and never seen anything as >> weird >> as this. Would it help if I attached my vhost config? >> >> Surely I don't need to specify a base href in my html unless I >> plan to >> use relative urls in my image tags - which I'm not. All my image/css >> links are absolute (albeit on the same host), and those are >> working fine. >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.agavi.org/mailman/listinfo/users > > > _______________________________________________ > users mailing list > [email protected] > http://lists.agavi.org/mailman/listinfo/users > _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
