[Prev] Thread [Next] |
[Prev] Date [Next]
[modwsgi] Re: SSL testing + error loging
Mon Jun 22 05:00:39 2009
On Jun 20, 1:07 pm, Graham Dumpleton <[EMAIL PROTECTED]>
> 2009/6/20 gert <[EMAIL PROTECTED]>:
> > On Jun 20, 7:54 am, Graham Dumpleton <[EMAIL PROTECTED]>
> > wrote:
> >> 2009/6/20 Nimrod A. Abing <[EMAIL PROTECTED]>:
> >> > On Sat, Jun 20, 2009 at 2:46 AM, gert<[EMAIL PROTECTED]> wrote:
> >> >> for me all the SSL testing seem to work, except i can not explain why
> >> >> in my daemon log i get reference to port 443 while i did put this as
> >> >> urlhttps://192.168.1.17:81/appwsgi/www/user/user.htm
> >> > You probably have another config file being loaded that sets up
> >> > mod_ssl on port 443. Check /etc/apache2/sites-enabled, assuming you
> >> > are on Debian/Ubuntu and that you are doing Apache configs "the Debian
> >> > way".
> >> From what I have seen before Gert ignores standard Apache
> >> configuration files and creates his own from scratch with everything
> >> in the same file. A lot of the time he just doesn't do things in
> >> normal ways and not surprised he has so many problems.
> >> Anyway, his problems are possibly because hist port 80 isn't even in a
> >> VirtualHost. If you are going to use VirtualHost you have to be
> >> consistent about it and use it for everything in a sane way.
> > Nope its for quickly testing daemon mode and embedded mode at the same
> > time on the same document root
> > embeddedhttps://192.168.1.17:80/appwsgi/www/user/user.htm
> > daemonhttps://192.168.1.17:81/appwsgi/www/user/user.htm(virtual host
> > part)
> > after some investigation i think 443 has to do with the client forcing
> > it I think.
> > Now how about the log files and stderr from daemon
> >https://192.168.1.17:81/appwsgi/www/user/user.htmgeting into embedded
> > log w80 and server wsgi messages getting into the correct daemon log
> > w81 ?
> > PS the above apache conf is the complete apache conf :)
> Fix your use of VirtualHost. Once you start using VirtualHost, you
> shouldn't put stuff at global server scope for what is another server.
> So, move the port 80 related stuff into its own VirtualHost along side
> that for port 81.
Ok i will do some more testing with 2 virtual hosts.
But still, 81 stderr ending up in global server space doing it my way
(read wrong way) is something to look at not ?
You received this message because you are subscribed to the Google Groups
To post to this group, send email to [EMAIL PROTECTED]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at