Webware for Python

> I cannot break out of ThreadedAppServer with Ctrl+C whether at the
 > command prompt or running inside WingIDE.
 > The DebugAppServer can break out fine.
 > I'm on Win XP Pro with Python 2.4.1.

It works on my Win XP Pro and Py 2.4.1 (tried only command line 
(cmd.exe), not WingIDE), and in the code, I cannot see why there should 
be any difference between ThreadedAppServer and DebugAppServer in rc1.

If I run AppServer.bat using cmd.exe in the directory /Webware/WebKit 
and press Ctrl+C it says "Exiting AppServer due to keyboard interrupt" 
and shuts down.

-- Chris

On 11/12/05, Christoph Zwerschke <cito@...> wrote:
>  > I cannot break out of ThreadedAppServer with Ctrl+C whether at the
>  > command prompt or running inside WingIDE.
>  > The DebugAppServer can break out fine.
>  > I'm on Win XP Pro with Python 2.4.1.
>
> It works on my Win XP Pro and Py 2.4.1 (tried only command line
> (cmd.exe), not WingIDE), and in the code, I cannot see why there should
> be any difference between ThreadedAppServer and DebugAppServer in rc1.
>
> If I run AppServer.bat using cmd.exe in the directory /Webware/WebKit
> and press Ctrl+C it says "Exiting AppServer due to keyboard interrupt"
> and shuts down.
>
> -- Chris

Well I do have a couple local mods to the source although I don't see
how they would be related. Also, I only really use the Debug Server on
my local Windows box. And on production, under Linux, I have no
problems.

Since it works for you and no one else has reported a problem, let's
go ahead and release.

If you're making the release from the repository (instead of renaming
rc1) then please test again.


-Chuck

Just checked the current trunk under WinXP + Py2.4.1 and I'm still 
experiencing no problems breaking out from th app server with Ctrl/C.

So I will proceed and release 0.9 today. According to Murphy we will not 
find the real bugs until shortly after the release anyway ;-) But since 
the release procedures and tools are now well documented, it will not be 
such a big thing anymore to make a 0.9.1 release.

Another issue: Currently, the 0.8.1 docs have been made available on the 
w4py.org server by copying the whole Webware tree to the w4py homeapge 
context. I think this is bad, because it does not only make the docs 
available, but also all the Python servlets anywhere in the 
distribution. I think that is not really good for the stability and 
security of the server. My suggestion is to install the 0.9 release on 
w4py.org. This allows to serve the documentation without making the 
whole tree available.

But I think it would not be so good to make such changes on the server 
this weekend together with the release of 0.9 since in case anything 
goes wrong people who want to download 0.9 will be frustrated. So I will 
probably make the update next weekend. Is that ok?

-- Chris

Or should I update the w4py.org server to 0.9 before making the release 
in order to have another real-world test?

-- Chris

On 11/13/05, Christoph Zwerschke <cito@...> wrote:
> Or should I update the w4py.org server to 0.9 before making the release
> in order to have another real-world test?
>
> -- Chris

I suggest making the release.

Regarding w4py.org, I'm not sure what specific security issues you're
referring to with regards to having the whole tree available. As long
as the .py files and other scripts are not executed by the web server,
we'll be fine. If they are, we can fix it or restrict to just docs
like you suggest. We already have access to the .py files on a
continuous basis:

http://svn.w4py.org/Webware/trunk/WebKit/HTTPRequest.py

But an installed copy of Webware has the unpacked docs as well--and
the .py files in that copy are nothing new.

-Chuck

> Regarding w4py.org, I'm not sure what specific security issues you're
> referring to with regards to having the whole tree available. As long
> as the .py files and other scripts are not executed by the web server,
> we'll be fine.

They ARE executed, that's what I'm talking about. For example,
http://w4py.org/Webware/WebKit/Examples/Welcome.py
http://w4py.org/Webware/WebKit/Admin/Main.py

The reason is that the whole Webware tree has been copied to the default 
context, so everything is available and executable under Webware.

The new Webware release has default contexts for displaying only the 
docs, so it would not be needed to copy the whole tree to the default 
context. Another and more efficient variant is letting Apache serve the 
docs directly, and not Webware.

-- Chris

Ok, I've fixed all that and updated the w4py.org server already. It now 
runs on Webware 0.9, and the docs are served directly by the webserver. 
The new releases and online docs are also available via SourceForge.

-- Chris