Unfortunately, since the server is running production, I dont feel comfortable placing apache on there - it is part of our short term plan, however. Do you think I could read the request that comes in to the regular site to see if the url has http, then redirect it from there? I would feel more comfortable making a change to this one site rather than a sweeping server change.
Thanks On Fri, Mar 14, 2008 at 1:13 PM, Aparajita Fishman < [EMAIL PROTECTED]> wrote: > > But when the (more common) url is: > > http://site1.domain.com > > > > They get the default page in the web folder. So apparently, the > > request > > does not come across as 443. Or the a4d vhosts file does not > > recognize > > https:// as equivalent to :443 > > > > Is there a way around this? > > The port is only recognized if it is part of the URL. https requests > can in fact be made on a port other than 443. Currently I have no way > of switching the virtual host based on the secure status. That would > be a good feature request. > > The only workaround I can think of is if you are using apache in front > of 4D, you could rewrite https requests to append :443 to the Host > header when they are forwarded to 4D. > > Regards, > > Aparajita > www.aparajitaworld.com > > "If you dare to fail, you are bound to succeed." > - Sri Chinmoy | www.srichinmoy.org > > > _______________________________________________ > Active4D-dev mailing list > [email protected] > http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev > Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/ > -- Thanks, Michael Check _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
