How does 0.36 work with the included wsgiserver and SSL?

136 views
Skip to first unread message

W. Martin Borgert

unread,
Aug 22, 2011, 8:01:32 PM8/22/11
to we...@googlegroups.com
Hi,

I just tried to run my web.py application with 0.36 instead of
0.34. Now HTTPS does not work anymore, HTTP is used instead.

The cookbook example http://webpy.org/cookbook/ssl seems to be
out of date in respect to web.py 0.36.

There are wrong imports in the wsgiserver/ssl* files btw.,
because cherrypy/ does not necessarily exist.

Any hints? TIA!

PriceChild

unread,
Sep 12, 2011, 7:07:45 AM9/12/11
to web.py
Just wanting to 'bump' this as I see the same issue but no response?

On Aug 23, 1:01 am, "W. Martin Borgert" <deba...@debian.org> wrote:
> Hi,
>
> I just tried to run my web.py application with 0.36 instead of
> 0.34. Now HTTPS does not work anymore, HTTP is used instead.
>
> The cookbook examplehttp://webpy.org/cookbook/sslseems to be

Anand Chitipothu

unread,
Sep 12, 2011, 7:26:20 AM9/12/11
to we...@googlegroups.com
2011/8/23 W. Martin Borgert <deb...@debian.org>:

Can you please try changing:

from cherrypy import wsgiserver

to:

from web import wsgiserver

in wsgiserver/ssl* files?

The wsgiserver code suggests that the old way to specifying SSL
configuration still works.

Anand

Joseph Price

unread,
Sep 12, 2011, 9:31:47 AM9/12/11
to we...@googlegroups.com
Sorry for potentially wasting time but I'm not getting errors on imports.

The exact output I'm getting is:

/usr/lib/python2.4/site-packages/web/wsgiserver/__init__.py:1701:
DeprecationWarning: SSL attributes are deprecated in CherryPy 3.2, and
will be removed in CherryPy 3.3. Use an ssl_adapter attribute instead.
DeprecationWarning

Looking at 'netstat', I can see python has only openned 8080, nothing for ssl.

> --
> You received this message because you are subscribed to the Google Groups "web.py" group.
> To post to this group, send email to we...@googlegroups.com.
> To unsubscribe from this group, send email to webpy+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/webpy?hl=en.
>
>

Anand Chitipothu

unread,
Sep 12, 2011, 12:29:04 PM9/12/11
to we...@googlegroups.com
2011/9/12 Joseph Price <price...@ubuntu.com>:

> Sorry for potentially wasting time but I'm not getting errors on imports.
>
> The exact output I'm getting is:
>
> /usr/lib/python2.4/site-packages/web/wsgiserver/__init__.py:1701:
> DeprecationWarning: SSL attributes are deprecated in CherryPy 3.2, and
> will be removed in CherryPy 3.3. Use an ssl_adapter attribute instead.
>  DeprecationWarning

That is a warning, nothing to worry about it. CherryPy WSGIserver has
added a new way to pass these parameters and the old way has been
deprecated.

> Looking at 'netstat', I can see python has only openned 8080, nothing for ssl.

8080 is the default port. Try accessing https://localhost:8080/ or
pass 443 as argument to your script.

Anand

Joseph Price

unread,
Sep 12, 2011, 3:38:23 PM9/12/11
to we...@googlegroups.com
>> Looking at 'netstat', I can see python has only openned 8080, nothing for ssl.
>
> 8080 is the default port. Try accessing https://localhost:8080/ or
> pass 443 as argument to your script.

Either way, http not https.

David Caro

unread,
Nov 2, 2011, 11:57:44 AM11/2/11
to web.py

Brent Uemura

unread,
Nov 6, 2011, 2:14:17 PM11/6/11
to we...@googlegroups.com

Right.  So if you want port 443, you'll have to explicitly set it when you start the app:

$ sudo python code.py 443 

Then you can hit your app via regular https:   https://localhost

If you don't it defaults to 8080

$ python code.py

So you'll need to append 8080 to the URL:  https://localhost:8080

It still uses ssl, just on a different port. 

-Brent


PriceChild

unread,
Nov 28, 2011, 10:35:40 AM11/28/11
to web.py
@Brent Its listenning as a standard web server, no ssl.

@David that's what I've followed as far as I know.

@Anand I might try that but I find it odd noone else is having
issues... I'm hoping its my code's fault and not web.py's, seen as
others apparently aren't having an issue?

On Nov 6, 7:14 pm, Brent Uemura <brent.uem...@gmail.com> wrote:
> Right.  So if you want port 443, you'll have to explicitly set it when you
> start the app:
>
> $ sudo python code.py 443
>
> Then you can hit your app via regular https:  https://localhost
>
> If you don't it defaults to 8080
>
> $ python code.py
>
> So you'll need to append 8080 to the URL:  https://localhost:8080
>
> It still uses ssl, just on a different port.
>
> -Brent
>

> On Wed, Nov 2, 2011 at 11:57 AM, David Caro <david.caro.al...@gmail.com>wrote:
>
>
>
>
>
>
>
> > Try this:
> >http://groups.google.com/group/webpy/browse_thread/thread/bbeb3fc7f24...

PriceChild

unread,
Nov 30, 2011, 6:50:20 AM11/30/11
to web.py
Swapping back to web.py 0.32 and running the example ssl code I got a
warning that I hadn't installed pyOpenSSL. I installed that and it
worked fine...

Back to web.py 0.36 and I'm back to it bringing up only a http server,
no ssl.

Any help please?

PriceChild

unread,
Nov 30, 2011, 6:57:05 AM11/30/11
to web.py
I've just grabbed the latest version of web.py from github and its now
working perfectly... I even get 'https' as the startup line when on
0.32 i got 'http' regardless.

So, I hope this proves its web.py's fault and not mine... might have a
look later to see what's changed and make that change to 0.36 as I'm
sure there's lots of nastiness in the latest version... if anyone
wants to save me the effort be my guest ;-)

Joseph Price

W. Martin Borgert

unread,
Feb 2, 2012, 6:53:25 PM2/2/12
to we...@googlegroups.com
On 2011-11-30 03:57, PriceChild wrote:
> I've just grabbed the latest version of web.py from github and its now
> working perfectly... I even get 'https' as the startup line when on
> 0.32 i got 'http' regardless.

I can confirm that the current github version seems to run the
first SSL example from http://webpy.org/cookbook/ssl perfectly.
Are there any plans to release 0.37 soon?

Anand Chitipothu

unread,
Feb 2, 2012, 11:37:38 PM2/2/12
to we...@googlegroups.com
2012/2/3 W. Martin Borgert <deb...@debian.org>:

Yes. I'm trying to fix some open bugs and update the cherrypy server
to the latest. It should be ready in a week or two.

Anand

Brent Uemura

unread,
Feb 3, 2012, 12:27:53 AM2/3/12
to we...@googlegroups.com

Thanks for fixing the SSL exception crash.  Looking forward to the release.

-Brent

W. Martin Borgert

unread,
Feb 3, 2012, 4:09:16 AM2/3/12
to we...@googlegroups.com
On 2012-02-03 10:07, Anand Chitipothu wrote:
> 2012/2/3 W. Martin Borgert <deb...@debian.org>:
> > Are there any plans to release 0.37 soon?
>
> Yes. I'm trying to fix some open bugs and update the cherrypy server
> to the latest.

This will be cherrypy 3.2.2?

> It should be ready in a week or two.

Many thanks in advance!

W. Martin Borgert

unread,
May 19, 2012, 5:58:54 AM5/19/12
to we...@googlegroups.com
On 2012-02-03 10:07, Anand Chitipothu wrote:
> 2012/2/3 W. Martin Borgert <deb...@debian.org>:
> > Are there any plans to release 0.37 soon?
>
> Yes. I'm trying to fix some open bugs and update the cherrypy server
> to the latest. It should be ready in a week or two.

Just a ping: Can we expect 0.37 soon?

TIA & Cheers
Reply all
Reply to author
Forward
0 new messages