|Anonymous | Login | Signup for a new account||07-15-2019 11:18 PDT|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Advanced Details [ Jump to Notes ]||[ View Simple ] [ Issue History ] [ Print ]|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0004239||[Resin]||minor||always||09-30-10 10:52||01-10-11 18:49|
|ETA||none||Fixed in Version||4.0.15||Product Version||4.0.11|
|Summary||0004239: server returning 304 messages|
(rep by Jamison Novak)
Here's what I see from the broken instance:
[root@exertus log]# telnet 192.168.0.10 80
Connected to foo.com (192.168.0.10).
Escape character is '^]'.
GET /test/index.html HTTP/1.0
HTTP/1.0 304 Not Modified
Last-Modified: Thu, 31 Dec 2009 17:32:15 GMT
Expires: Thu, 30 Sep 2010 05:28:56 GMT
Set-Cookie: JSESSIONID=aaaCij59LZlhUaHXuhHTs; path=/
Date: Thu, 30 Sep 2010 05:28:51 GMT
Connection closed by foreign host.
I would expect a 500 error or a 404, but a 304? That is just odd. That URL is actually an alias, just so we're clear:
<real-path regexp="^/test" target="/usr/local/www/test/wad"/>
The last thing in the watchdog.log is the starting of the instance. The process is running, it's obviously responding to HTTP requests (although not in the manner I would expect), but there is no wad-stdout.log and the website is not available.
Going back in and stopping and then restarting the instance brought the site back up.
I'm attaching a stack trace of the watchdog process, as well as the wad instance before the restart.
|Steps To Reproduce|
|09-30-10 10:52||ferg||New Issue|
|01-10-11 18:49||ferg||Note Added: 0004907|
|01-10-11 18:49||ferg||Assigned To||=> ferg|
|01-10-11 18:49||ferg||Status||new => closed|
|01-10-11 18:49||ferg||Resolution||open => fixed|
|01-10-11 18:49||ferg||Fixed in Version||=> 4.0.15|
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed.|
25 unique queries executed.