David Zülke wrote: > > Daniel, > > you have to adjust Apache's ServerName setting, too - changing Listen > alone is not enough.
I have identical virtual host setup on a different box, running an older release of Agavi (svn 1486, see http://trac.agavi.org/ticket/499) and it works fine. If I update Agavi, and my app (to accomodate the considerable API changes), the behaviour of Agavi's redirect API changes as I describe in the ticket. > > $routing->getBaseHref() should return the URL without the port, too. > This is an indication that there's something wrong with your > webserver setup, and Agavi cannot determine the host. Check a phpinfo > (), I'm pretty sure the port doesn't appear there either. Or are you > using a proxy, load balancer, anything like that? No proxy, no load balancer. Direct TCP connects. phpinfo() on the same virtual host correctly shows the port. Mod_rewrite may be having something to do with it, since when I print_r($_SERVER) from index.php with the .htaccess enabling mod_rewrite, the SERVER_PORT seems to have been clobbered. The fact remains though that Agavi used to simply send an absolute URL in the Location header, as opposed to a full URL including protocol now - ie, it seems unable to recognise that I'm doing a redirect to a generated route in my own app. I'm either overlooking something really fundamental here, or something has changed radically in Agavi. _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
