This list is closed, nobody may subscribe to it.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(149) |
Jun
(174) |
Jul
(41) |
Aug
(118) |
Sep
(72) |
Oct
(111) |
Nov
(69) |
Dec
(147) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(242) |
Feb
(276) |
Mar
(363) |
Apr
(704) |
May
(183) |
Jun
(209) |
Jul
(173) |
Aug
(230) |
Sep
(80) |
Oct
(306) |
Nov
(338) |
Dec
(291) |
2002 |
Jan
(273) |
Feb
(294) |
Mar
(303) |
Apr
(463) |
May
(319) |
Jun
(182) |
Jul
(160) |
Aug
(140) |
Sep
(192) |
Oct
(302) |
Nov
(238) |
Dec
(176) |
2003 |
Jan
(179) |
Feb
(222) |
Mar
(256) |
Apr
(167) |
May
(139) |
Jun
(145) |
Jul
(113) |
Aug
(259) |
Sep
(146) |
Oct
(124) |
Nov
(143) |
Dec
(66) |
2004 |
Jan
(58) |
Feb
(128) |
Mar
(193) |
Apr
(228) |
May
(111) |
Jun
(107) |
Jul
(93) |
Aug
(78) |
Sep
(48) |
Oct
(99) |
Nov
(104) |
Dec
(119) |
2005 |
Jan
(115) |
Feb
(124) |
Mar
(86) |
Apr
(41) |
May
(52) |
Jun
(21) |
Jul
(32) |
Aug
(14) |
Sep
(52) |
Oct
(30) |
Nov
(19) |
Dec
(19) |
2006 |
Jan
(43) |
Feb
(35) |
Mar
(68) |
Apr
(21) |
May
(38) |
Jun
(46) |
Jul
(19) |
Aug
(38) |
Sep
(58) |
Oct
(15) |
Nov
(12) |
Dec
(30) |
2007 |
Jan
(49) |
Feb
(23) |
Mar
(29) |
Apr
(19) |
May
(33) |
Jun
(4) |
Jul
(10) |
Aug
(26) |
Sep
(2) |
Oct
(9) |
Nov
(1) |
Dec
(21) |
2008 |
Jan
(15) |
Feb
(3) |
Mar
(10) |
Apr
(8) |
May
(4) |
Jun
(2) |
Jul
(2) |
Aug
|
Sep
|
Oct
(2) |
Nov
(13) |
Dec
|
2009 |
Jan
(11) |
Feb
(4) |
Mar
|
Apr
(6) |
May
|
Jun
(16) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(9) |
2010 |
Jan
(6) |
Feb
(4) |
Mar
(2) |
Apr
(12) |
May
(20) |
Jun
(9) |
Jul
(7) |
Aug
|
Sep
(1) |
Oct
(5) |
Nov
|
Dec
(4) |
2011 |
Jan
|
Feb
|
Mar
(10) |
Apr
|
May
|
Jun
|
Jul
(9) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
(3) |
Nov
(8) |
Dec
(11) |
2013 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(6) |
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
(2) |
Dec
|
2017 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(3) |
Dec
|
2020 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
2021 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2022 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
(2) |
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Mark P. <mar...@mo...> - 2009-12-20 23:32:55
|
On Dec 14, 2009, at 2:41 PM, Christoph Zwerschke wrote: > Thanks for the kind words, Mark. You are most welcome. Your efforts are greatly appreciated. After spending way too much time on various "web" tools, e.g. Django, jQuery and similar, I find webware provides a nice balance of features and simplicity. > There are no fundamental API changes between v0.9 and v1. > > But if you're updating from such an old version, you should recreate > the > working directory with MakeAppWorkDir, and copy the old context(s) and > changes in config settings over to the newly created directory. Understood. Many thanks, - Mark |
From: Christoph Z. <ci...@on...> - 2009-12-14 22:42:09
|
Thanks for the kind words, Mark. There are no fundamental API changes between v0.9 and v1. But if you're updating from such an old version, you should recreate the working directory with MakeAppWorkDir, and copy the old context(s) and changes in config settings over to the newly created directory. -- Christoph |
From: Mark P. <mar...@mo...> - 2009-12-14 21:01:24
|
I have been busy on other projects, and webware simply caused me no trouble so I haven't posted in a long while. Recently, a catastrophic hard drive crash forced me to rebuild a system and part of that was to re-install webware for an xml-rpc app built some years ago. I used 0.9 because that was what used before. However, I would like to catch up to the current version. Christoph et al have done such a great job of improving the product. I have poked through the release notes but still have the urge to ask this question: Are there any "gotchas" in moving from such an old version to the current release? TIA, - Mark Phillips |
From: Christoph Z. <ci...@on...> - 2009-12-06 21:40:26
|
Peter Lyons wrote: > (There are 10 total connection attempts from apache/mod_webkit to the > adapter then it just gives up). I get a 500 internal server error page from > apache in my browser. Hi Peter, I noticed the same problem on OpenSuse 11.2 two weeks ago and have already improved the mod_webkit adapter (in r8092) so that this should not happen any more. I'm planning to release a 1.0.x bugfix version and a 1.1 version of Webware including this fix soon. Meanwhile, you can use the workaround suggested by Oliver and Andreas. -- Christoph |
From: Peter L. <pe...@pe...> - 2009-12-06 18:26:46
|
On Sun, Dec 6, 2009 at 5:06 AM, Andreas Poisel <a.p...@ac...> wrote: > * Peter Lyons <pe...@pe...> [06.12.2009 08:20]: > > > I think you are probably correct that there is some IPv4/IPv6 issue at > play > > here, but I don't know what that would be exactly. > > Maybe we should mention how to quickly fix the problem: > > Either remove IPv6-related entries from /etc/hosts (should you not need > them) or change the apache configuration from something like > > <Location /PATH> > WKServer localhost PORT > [...] > </Location> > > to > > <Location /PATH> > WKServer 127.0.0.1 PORT > [...] > </Location> > > -- > Bye, Andreas > Yes, that fixed it! Thank you Andreas! |
From: Andreas P. <a.p...@ac...> - 2009-12-06 12:26:41
|
* Peter Lyons <pe...@pe...> [06.12.2009 08:20]: > I think you are probably correct that there is some IPv4/IPv6 issue at play > here, but I don't know what that would be exactly. Maybe we should mention how to quickly fix the problem: Either remove IPv6-related entries from /etc/hosts (should you not need them) or change the apache configuration from something like <Location /PATH> WKServer localhost PORT [...] </Location> to <Location /PATH> WKServer 127.0.0.1 PORT [...] </Location> -- Bye, Andreas |
From: Peter L. <pe...@pe...> - 2009-12-06 07:14:25
|
Webware is listening on 0.0.0.0 which means all configured IPv4 interfaces. That would include the loopback 127.0.0.1 address assigned to the lo interface: * root@mrpc:~# netstat -ntlp|grep 9000 tcp 0 0 0.0.0.0:9000 0.0.0.0:* LISTEN 4251/python root@mrpc:~# ifconfig lo lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1* root@mrpc:~# cat /etc/hosts 127.0.0.1 mrpc.peterlyons.com mrpc localhost.localdomain localhost plwiki.peterlyons.com plwiki stage.peterlyons.com stage # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback I think you are probably correct that there is some IPv4/IPv6 issue at play here, but I don't know what that would be exactly. On Sat, Dec 5, 2009 at 8:41 PM, Oliver Bock <ol...@g7...> wrote: > Is Webware listening on 127.0.0.1 or localhost? I think there can be a TCP > IP v4/v6 problem. > > |
From: Oliver B. <ol...@g7...> - 2009-12-06 04:40:41
|
Is Webware listening on 127.0.0.1 or localhost? I think there can be a TCP IP v4/v6 problem. On 06/12/2009, at 1:57 PM, Peter Lyons wrote: > Hi, > > I have been running webware on an ubuntu/apache/mod_webkit stack > for several years now with no problems. I upgraded to ubuntu 9.10 > and now apache cannot connect to the webkit app server. I've done > a good deal of troubleshooting, but I'm stuck. Here's what happens > in my apache error log when I browse to any URL handled by webkit: > > [Sat Dec 05 19:14:16 2009] [error] Can not open socket connection > to WebKit AppServer > [Sat Dec 05 19:14:16 2009] [error] Couldn't connect to AppServer, > attempt 10 of 10, sleeping 1 second(s) > [Sat Dec 05 19:14:17 2009] [error] timed out trying to connect to > appserver -- giving up. ... |
From: Gary P. <gar...@as...> - 2009-07-01 11:55:28
|
Wouldn't you know? This morning, I got another AssertionError... this time from http://ipaddress:8081/. I've turned off the EnableHTTP altogether. Thanks for pointing that out. On Jun 30, 2009, at 2:48, Christoph Zwerschke wrote: > Gary Perez schrieb: >> Upon closer inspection of the emailed AssertionErrors, it appeared >> that the proxy requests weren't actually hitting any of the >> VirtualHost domains for that box, but they were explicitly connecting >> to http://ipaddress:8080/. So it didn't really matter how I had the >> rewrite rules or virtual hosting configured. > > Ok, thanks for the feedback. Maybe I can improve the behavior when > WebKit is addressed as a proxy. Btw, you can disable the built-in > webserver on port 8080 and only listen to the app server port 8086. > Just set EnableHTTP = False in AppServer.config. Also, in the same > config file you can restrict the network interfaces at which the > application server will listen. I recommend setting > Host='localhost' to > only listen to the Apache on the same server. > > -- Christoph > > ---------------------------------------------------------------------- > -------- > _______________________________________________ > Webware-discuss mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webware-discuss > Gary Perez Advanced Simulation Technology inc. gar...@as... http://www.asti-usa.com/ |
From: Christoph Z. <ci...@on...> - 2009-06-30 18:47:28
|
Gary Perez schrieb: > Upon closer inspection of the emailed AssertionErrors, it appeared > that the proxy requests weren't actually hitting any of the > VirtualHost domains for that box, but they were explicitly connecting > to http://ipaddress:8080/. So it didn't really matter how I had the > rewrite rules or virtual hosting configured. Ok, thanks for the feedback. Maybe I can improve the behavior when WebKit is addressed as a proxy. Btw, you can disable the built-in webserver on port 8080 and only listen to the app server port 8086. Just set EnableHTTP = False in AppServer.config. Also, in the same config file you can restrict the network interfaces at which the application server will listen. I recommend setting Host='localhost' to only listen to the Apache on the same server. -- Christoph |
From: Gary P. <gar...@as...> - 2009-06-30 18:07:46
|
Just to followup. I eventually did upgrade the installation from 0.9.4 to 1.0.2 by installing it alongside the original directory & changing the webwareDir config. line inside my app working directory's Launch.py. Unfortunately, this is unrelated to the original problem. ------------------ Here's what I think was happening. The server (somehow) made its way onto a list of open proxy web servers. At that time, Apache2 was configured to be an open proxy... but I didn't know it. So I changed httpd.conf to remove the proxy- related functionality. But that didn't fix the AssertionErrors problem, it merely stopped the server from acting as a proxy. In fact, it caused the number of AssertionErrors to skyrocket from a few per day to approx. 100 in 2 hours. I'd originally had Apache configured with rewrite rules to route "normal" URLs through the AppServer... (e.g., requests to www.example.com got served through www.example.com/webkit/). Thinking that the unwanted proxy requests were hitting these "normal" URLs, I removed the rewrite rules. This had no effect on the errors; they kept coming in droves. Upon closer inspection of the emailed AssertionErrors, it appeared that the proxy requests weren't actually hitting any of the VirtualHost domains for that box, but they were explicitly connecting to http://ipaddress:8080/. So it didn't really matter how I had the rewrite rules or virtual hosting configured. Finally, I changed the port number inside my app working directory/ Configs/AppServer.config. Now (at least theoretically), the server's just kicking back 404s to everything connecting to 8080 instead of routing anything through WebKit & inducing the AssertionErrors. It'll work for now. If any of you have any suggestions as to a better way to fix the problem, I'd certainly welcome them. Thanks, -Gary On Jun 8, 2009, at 4:27, Christoph Zwerschke wrote: > Gary Perez schrieb: >> I use MakeAppWorkDir.py after each (new) installation. Is it possible >> to install the new version of Webware & then point the existing >> appworkdir to it in place of the older version? >> >> Or should it be run again to create a fresh appworkdir, copy context >> directories & reconfigure? > > This is only required if you're updating from a really old version. > If your're running 0.9.1 or newer, you can simply update Webware > itself > without any changes in the app work dirs. > > I recommend moving the old version to /usr/local/Webware.old and then > installing the current version as /usr/local/Webware. Then no > changes to > the working dirs will be needed, and if it does not work as expected, > you can easily revert the update. > > -- Christoph |
From: Christoph Z. <ci...@on...> - 2009-06-29 18:49:44
|
Thanks for the patches, Justin, they are welcome. I'm currently working on 1.1 which will require Py >= 2.4. There I have already replaced such checks with "isinstance(..., basestring)" which effectively does the same but is a newer idiom. But I will also backport this to the 1.0.3 bugfix release. The 1.0.x versions will always compatible with Py >= 2.0. Here we need to import StringTypes from MiscUtils because it appeared only in newer Py vers. If you have more suggestions and patches, let me know. -- Christoph |
From: Justin A. <jus...@is...> - 2009-06-29 16:50:00
|
I've had to create some patches against Webware 1.0.2 for Python 2.3 compatibility. The comparison to StringType on Python 2.3 does not include Unicode strings. I'll inline the patches below: --- DocSupport/ClassList.py.orig Mon Jun 15 13:35:30 2009 +++ DocSupport/ClassList.py Mon Jun 15 13:36:10 2009 @@ -9,7 +9,7 @@ import os, re, sys from glob import glob -from types import StringType +from types import StringTypes def EmptyString(klass): @@ -155,7 +155,7 @@ klass.printList(file=file) def printForWeb(self, hierarchic=0, file=sys.stdout): - if type(file) is StringType: + if type(file) in StringTypes: file = open(file, 'w') close = 1 else: --- DocSupport/FileList.py.orig Mon Jun 15 13:35:43 2009 +++ DocSupport/FileList.py Mon Jun 15 13:38:40 2009 @@ -9,7 +9,7 @@ import os, sys from glob import glob -from types import StringType +from types import StringTypes class FileList: @@ -39,7 +39,7 @@ self._files.append(name) def printList(self, file=sys.stdout): - if type(file) is StringType: + if type(file) in StringTypes: file = open(file, 'w') close = 1 else: @@ -56,7 +56,7 @@ file.close() def printForWeb(self, file=sys.stdout): - if type(file) is StringType: + if type(file) in StringTypes: file = open(file, 'w') close = 1 else: I'd love for these to be included in Webware 1.0.3 Thanks, -Justin Akehurst Justin Akehurst Software Design Engineer - UI Isilon Systems, Inc www.isilon.com <http://www.isilon.com/> P +1-206-315-7500 F +1-206-315-7501 D +1-206-315-7576 <file:///C:\Documents%20and%20Settings\jakehurst\Application%20Data\Micr osoft\Signatures\isilon_logo.png> The Proven Leader in Scale-out NAS Simplicity and Value. Guaranteed <http://www.isilon.com/guarantee/> |
From: Justin A. <jus...@is...> - 2009-06-29 16:43:57
|
Thanks Christoph, I've taken your suggestions and applied them to my patchset for ThreadedAppServer for Webware 1.0.2, below: --- WebKit/ThreadedAppServer.py.orig Mon Jun 29 08:54:13 2009 +++ WebKit/ThreadedAppServer.py Mon Jun 29 09:39:28 2009 @@ -271,6 +271,20 @@ try: sock.bind(serverAddress) sock.listen(1024) + try: + import fcntl + except ImportError, e: + # Platform does not have fcntl module + pass + else: + fd = sock.fileno() + flags = fcntl.fcntl(fd, fcntl.F_GETFD) + try: + flags |= fnctl.FD_CLOEXEC + except AttributeError, e: + # Python 2.2 does not include FD_CLOEXEC + flags |= 1 + fcntl.fcntl(fd, fcntl.F_SETFD, flags) except Exception: print "Error: Can not listen for %s on %s" % ( handlerClass.settingPrefix, str(serverAddress)) Having this in the main distribution would be great! I have a few more suggestions for upstreaming patches, which I'll send to the list separately. -Justin Akehurst > -----Original Message----- > From: Christoph Zwerschke [mailto:ci...@on...] > Sent: Saturday, June 27, 2009 1:51 AM > To: Discussion of Webware for Python including feedback and proposals. > Subject: Re: [Webware-discuss] socket close-on-exec patch needed anymore on > ThreadedAppServer? > > Hi Justin, > > > I'm in the process of upgrading Webware to version 1.0.2 from version > 0.8.4 > > You probably mean 0.8.1? Please note that you should create a new app > work dir in this case (with MakeAppWorkDir) and move your contexts etc. > to the new app work dir, since some things have changed here. > > > We currently have a patch that we apply to the older version to add > > in socket close-on-exec within the ThreadedAppServer, like so: > > > > Do we need to reapply this patch to Webware 1.0.2, or was > > ThreadedAppServer rewritten to avoid this problem? > > No, it seems this patch has never been suggested. It makes sense when > your app forks its own processes, right? I can try to get this into > 1.0.3/1.1 (needs to be done carefully, because it works only on Unix, > and F_SETFD and FD_CLOEXEC may not be defined in all Py versions). > > If you want to do it with Webware 1.0.2, you need to apply your patch > after line 273 of ThreadedAppServer.py. > > -- Christoph > > ------------------------------------------------------------------------ ---- > -- > _______________________________________________ > Webware-discuss mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webware-discuss |
From: Christoph Z. <ci...@on...> - 2009-06-27 08:50:02
|
Hi Justin, > I'm in the process of upgrading Webware to version 1.0.2 from version 0.8.4 You probably mean 0.8.1? Please note that you should create a new app work dir in this case (with MakeAppWorkDir) and move your contexts etc. to the new app work dir, since some things have changed here. > We currently have a patch that we apply to the older version to add > in socket close-on-exec within the ThreadedAppServer, like so: > > Do we need to reapply this patch to Webware 1.0.2, or was > ThreadedAppServer rewritten to avoid this problem? No, it seems this patch has never been suggested. It makes sense when your app forks its own processes, right? I can try to get this into 1.0.3/1.1 (needs to be done carefully, because it works only on Unix, and F_SETFD and FD_CLOEXEC may not be defined in all Py versions). If you want to do it with Webware 1.0.2, you need to apply your patch after line 273 of ThreadedAppServer.py. -- Christoph |
From: Justin A. <jus...@is...> - 2009-06-26 20:19:04
|
I'm in the process of upgrading Webware to version 1.0.2 from version 0.8.4 We currently have a patch that we apply to the older version to add in socket close-on-exec within the ThreadedAppServer, like so: --- Webware.orig/WebKit/ThreadedAppServer.py Thu Mar 21 11:40:40 2002 +++ Webware/WebKit/ThreadedAppServer.py Tue Oct 1 14:11:28 2002 @@ -26,6 +26,7 @@ import select import socket import threading +import fcntl import time import errno import traceback @@ -105,6 +106,7 @@ # @@ 2001-05-30 ce: another hard coded number: @@jsl- not everything needs to be configurable.... self.mainsocket.listen(1024) + fcntl.fcntl(self.mainsocket.fileno(), fcntl.F_SETFD, 1) self.recordPID() print "Ready\n" We are running FreeBSD 6.1 Do we need to reapply this patch to Webware 1.0.2, or was ThreadedAppServer rewritten to avoid this problem? -Justin Akehurst Justin Akehurst Software Design Engineer - UI Isilon Systems, Inc www.isilon.com P +1-206-315-7500 F +1-206-315-7501 D +1-206-315-7576 The Proven Leader in Scale-out NAS Simplicity and Value. Guaranteed |
From: Christoph Z. <ci...@on...> - 2009-06-08 20:27:10
|
Gary Perez schrieb: > I use MakeAppWorkDir.py after each (new) installation. Is it possible > to install the new version of Webware & then point the existing > appworkdir to it in place of the older version? > > Or should it be run again to create a fresh appworkdir, copy context > directories & reconfigure? This is only required if you're updating from a really old version. If your're running 0.9.1 or newer, you can simply update Webware itself without any changes in the app work dirs. I recommend moving the old version to /usr/local/Webware.old and then installing the current version as /usr/local/Webware. Then no changes to the working dirs will be needed, and if it does not work as expected, you can easily revert the update. -- Christoph |
From: Gary P. <gar...@as...> - 2009-06-08 18:51:27
|
What's the best way to upgrade a current installation to the latest version? The latest info regarding this (that I could locate) is from 2006: http://www.mail-archive.com/web...@li.../ msg08235.html I use MakeAppWorkDir.py after each (new) installation. Is it possible to install the new version of Webware & then point the existing appworkdir to it in place of the older version? Or should it be run again to create a fresh appworkdir, copy context directories & reconfigure? Thanks, -Gary On Jun 2, 2009, at 4:57, Christoph Zwerschke wrote: > Gary Perez schrieb: >> Various lines exist in the log files, e.g.: >> ... >> ... "GET http://proxyjudge1.proxyfire.net/fastenv HTTP/1.1" ... > > I tried requesting such URLs with telnet, but was not able to > reproduce > the problem. > > Can you update to the latest Webware version and check whether that > works better? You can download it at > > http://downloads.sourceforge.net/webware/Webware-1.0.2b1.tar.gz > > I'd like to get feedback conerning 1.0.2b1 anwyway, since I want to > publish 1.0.2 soon. > > -- CHristoph > > > > > ---------------------------------------------------------------------- > -------- > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the > latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Webware-discuss mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webware-discuss > -- Gary Perez :: Interwebs Guy Advanced Simulation Technology inc. gar...@as... http://www.asti-usa.com/ |
From: Christoph Z. <ci...@on...> - 2009-06-07 19:44:35
|
Webware for Python 1.0.2 has been released. This is the second bugfix release for Webware for Python release 1.0, mainly fixing some problems and shortcomings of the PSP plug-in. See the WebKit and PSP release notes for details. Webware for Python is a suite of Python packages and tools for developing object-oriented, web-based applications. The suite uses well known design patterns and includes a fast Application Server, Servlets, Python Server Pages (PSP), Object-Relational Mapping, Task Scheduling, Session Management, and many other features. Webware is very modular and easily extended. Webware for Python is well proven and platform-independent. It is compatible with multiple web servers, database servers and operating systems. Check out the Webware for Python home page at http://www.w4py.org |
From: Christoph Z. <ci...@on...> - 2009-06-02 20:57:08
|
Gary Perez schrieb: > Various lines exist in the log files, e.g.: > ... > ... "GET http://proxyjudge1.proxyfire.net/fastenv HTTP/1.1" ... I tried requesting such URLs with telnet, but was not able to reproduce the problem. Can you update to the latest Webware version and check whether that works better? You can download it at http://downloads.sourceforge.net/webware/Webware-1.0.2b1.tar.gz I'd like to get feedback conerning 1.0.2b1 anwyway, since I want to publish 1.0.2 soon. -- CHristoph |
From: Gary P. <gar...@as...> - 2009-06-02 19:27:43
|
Various lines exist in the log files, e.g.: 89.188.112.122 - - [01/Jun/2009:17:31:19 -0400] "POST http:// ixdatahost.ru/proxy5/check.php HTTP/1.1" 404 293 "http://de58bfe3d3/" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)" 61.139.105.163 - - [27/May/2009:19:43:27 -0400] "GET http:// www.google.com/intl/zh-CN/ HTTP/1.1" 404 289 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)" 61.139.105.163 - - [30/May/2009:06:23:25 -0400] "GET http:// proxyjudge1.proxyfire.net/fastenv HTTP/1.1" 404 296 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)" 88.80.7.248 - - [25/May/2009:07:02:08 -0400] "GET http://88.80.7.248/ pp/anp.php?a=UV%5CHWQFY%40L%5CUEZ&b=1155&c=88a8 HTTP/1.1" 404 285 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)" On Jun 2, 2009, at 2:15, Christoph Zwerschke wrote: > Gary Perez schrieb: >> I'm surprised nobody has had this happen before. Googling the >> specific error turns up zero hits. I must be an edge-case. > > You config looks ok. Can you see the corresponding entries in the > Apache > access log? > > -- Christoph > > ---------------------------------------------------------------------- > -------- > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the > latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Webware-discuss mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webware-discuss > -- Gary Perez :: Interwebs Guy Advanced Simulation Technology inc. gar...@as... http://www.asti-usa.com/ |
From: Christoph Z. <ci...@on...> - 2009-06-02 18:14:46
|
Gary Perez schrieb: > I'm surprised nobody has had this happen before. Googling the > specific error turns up zero hits. I must be an edge-case. You config looks ok. Can you see the corresponding entries in the Apache access log? -- Christoph |
From: Gary P. <gar...@as...> - 2009-06-01 21:57:35
|
Hi Christoph, For each of the domains hosted under this installation, I have: NameVirtualHost [ipaddr]:80 <VirtualHost [ipaddr]:80> ServerName [domain].com ServerAlias [domain].com *.[domain].com DocumentRoot /var/www/[domain] </VirtualHost> But I also employ a number of rewrite rules (within the VirtualHost directive) for those which primarily use the webkit application server (the "wk" part of the URL): RewriteEngine On RewriteRule ^/wk/(.*) /$1 [R] RewriteRule ^/js/(.*) /js/$1 [PT] RewriteRule ^/gfx/(.*) /gfx/$1 [PT] RewriteRule ^/logos/(.*) /logos/$1 [PT] RewriteRule ^/screens/(.*) /screens/$1 [L,PT] RewriteRule ^/(.*) /wk/$1 [L,PT] I killed the application server earlier today to halt the increasing # of emailed tracebacks/errors. I'm surprised nobody has had this happen before. Googling the specific error turns up zero hits. I must be an edge-case. Thanks, -Gary On Jun 1, 2009, at 5:30, Christoph Zwerschke wrote: > Gary Perez schrieb: >> I looked up this "proxy5/check.php" thing in Google & it indicates >> (?) some type of proxy abuse (led me to: http://wiki.apache.org/ >> httpd/ >> ProxyAbuse). So I changed the config. in httpd.conf, but that only >> seemed to generate more errors & emails. > > Hi Gary, > > I did not come across these errors so far. They do not appear in > the log > of our Webware server at w4py.org either. > > What did you change in the config? Did you set the ServerName? I think > that should solve the issue. > > -- Christoph > > > > ---------------------------------------------------------------------- > -------- > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the > latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Webware-discuss mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webware-discuss > -- Gary Perez :: Interwebs Guy Advanced Simulation Technology inc. gar...@as... http://www.asti-usa.com/ |
From: Christoph Z. <ci...@on...> - 2009-06-01 21:29:25
|
Gary Perez schrieb: > I looked up this "proxy5/check.php" thing in Google & it indicates > (?) some type of proxy abuse (led me to: http://wiki.apache.org/httpd/ > ProxyAbuse). So I changed the config. in httpd.conf, but that only > seemed to generate more errors & emails. Hi Gary, I did not come across these errors so far. They do not appear in the log of our Webware server at w4py.org either. What did you change in the config? Did you set the ServerName? I think that should solve the issue. -- Christoph |
From: Gary P. <gar...@as...> - 2009-06-01 20:48:22
|
Hi all, I've been receiving email notifications for this type of error (traceback at the end) since going live with one of my Webware-based sites back in October. Only recently has it ramped up to be troublesome. The AssertionError happens every time, but the URL shown in the traceback changes. I looked up this "proxy5/check.php" thing in Google & it indicates (?) some type of proxy abuse (led me to: http://wiki.apache.org/httpd/ ProxyAbuse). So I changed the config. in httpd.conf, but that only seemed to generate more errors & emails. My question, then, is: Have any of you run into something like this before? If so, did you successfully stop it from happening & what did you do? Otherwise, anybody have any suggestions? Running Ww 0.9.4 on RH/CentOS with Apache 2.0.54 and mod_webkit2. Thanks for any guidance, -Gary WebKit caught an exception while processing a request for "None" at Mon Jun 1 15:29:50 2009 (timestamp: 1243884590.91). The plain text traceback from Python is printed below and the full HTML error report from WebKit is attached. Traceback (most recent call last): File "/usr/local/Webware-0.9.4/WebKit/Application.py", line 645, in runTransaction servlet = findServlet(trans) File "/usr/local/Webware-0.9.4/WebKit/URLParser.py", line 70, in findServletForTransaction return self.parse(trans, trans.request().urlPath()) File "/usr/local/Webware-0.9.4/WebKit/URLParser.py", line 314, in parse return fpp.parse(trans, requestPath) File "/usr/local/Webware-0.9.4/WebKit/URLParser.py", line 387, in parse assert not requestPath or requestPath.startswith('/'), \ AssertionError: Not what I expected: 'http://206.51.235.166/proxy5/ check.php' |