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
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.
--
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
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/webware-discuss@lists.sourceforge.net/
msg08235.html
I use MakeAppWorkDir.py after each (new) installation. Is it
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
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
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://
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
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
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
10 matches
Mail list logo
