BTW - I've reviewed the changes, and they look ok;

I've only tested this 10 minutes locally on a Windows XP machine - so
basic sanity tests work:  admin, T3, other things etc. all "work as
expected".   The code changes wouldn't lead me to expect any
surprises.

On Dec 5, 7:28 pm, "Yarko Tymciurak" <[EMAIL PROTECTED]> wrote:
> Konrad -
> Could you try an experiment?   temporarily replace your gluon/wsgiserver.py
>  withhttp://www.cherrypy.org/browser/tags/cherrypy-3.1.1/cherrypy/wsgiserv...
>
> There is already a gluon/__init__.py, so dowload it somewhere else and
> rename it to wsgiserver.py before you move it over.
>
> Looking throuhg the 3.1.1 source changes, I think this may address this -
> and other similar instances like this we have been seeing.
>
> Let us know.
>
> Thanks,
> Yarko
>
> On Fri, Dec 5, 2008 at 7:17 PM, Yarko Tymciurak <[EMAIL PROTECTED]> wrote:
> > I'm just looking through the difference between the 3.1.0b1 cherrypy
> > currently in web2py, and the 3.1.1;  I think we may want to upgrade to
> > 3.1.1;
> > I'll test this a little....
>
> > On Fri, Dec 5, 2008 at 6:41 PM, mdipierro <[EMAIL PROTECTED]> wrote:
>
> >> This looks like be bug in "gluon/wsgiserver.py" which is the cherrypy
> >> wsgiserver. I will look into it but because it is (the only) third
> >> party package in there it is unlikely it will be fixed soon.
>
> >> I suggest you setup apache with mod_wsgi and bypass compleyely the
> >> built-in web server for production application, in particular for
> >> serving large files.
>
> >> Massimo
>
> >> On Dec 5, 6:16 pm, Konrad <[EMAIL PROTECTED]> wrote:
> >> > Hello,
>
> >> > first: compliments for web2py! I've built my first we application, and
> >> > it's REALLY easy (and I have not even done any python before...). But
> >> > now I am completely stuck. I lost my last hairs trying to figure why
> >> > the QuickTime Plugin would play my *.mov files if I access the site
> >> > locally, but not if I access it from remote - thanks to QuickTime for
> >> > a question mark being the only error message. :(
>
> >> > It looks like a bug to me:
>
> >> > 1) Running web2py Version 1.51 (2008-11-19 14:48:02) on a fully
> >> > patched Mac OS X 10.4.11 in an administrative account.
>
> >> > 2) Serving a file /appname/static/d001.mov (size: 1.5MB)
>
> >> > 3) Accessing the file on the same computer (Mac) with:
> >>http://mypublicip:8000/appname/static/d001.mov
> >> > Works (both playing in QT plugin or 'Save link as ...')
>
> >> > 4) Accessing the file from a different computer (both playing or 'save
> >> > link as...') results in the first 60kB of the file being downloaded,
> >> > and then the download aborts. Inspecting the contents of the file, the
> >> > first 60kB are  the beginning of the movie-data, but then there is a
> >> > web2py-error message in the file:
>
> >> > HTTP/1.1 500 Internal Server Error
> >> > Content-Length: 332
> >> > Content-Type: text/plain
>
> >> > Traceback (most recent call last):
> >> > File "gluon/wsgiserver.pyc", line 765, in communicate
> >> > File "gluon/wsgiserver.pyc", line 488, in respond
> >> > File "gluon/wsgiserver.pyc", line 509, in _respond
> >> > File "gluon/wsgiserver.pyc", line 569, in write
> >> > File "<string>", line 1, in sendall
> >> > error: (35, 'Resource temporarily unavailable')
>
> >> > I tried this within two different networks (within home and within
> >> > work), with different XP Pro clients (mostly failed), one Vista
> >> > Enterprise client (mostly worked), but always using the same Mac-
> >> > Laptop as server.
>
> >> > Any idea what could be the problem or how I could approach this to
> >> > debug?
>
> >> > Thanks a lot,
> >> > Konrad
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to