Mantis - Resin
|
|||||
Viewing Issue Advanced Details | |||||
|
|||||
ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
4239 | minor | always | 09-30-10 10:52 | 01-10-11 18:49 | |
|
|||||
Reporter: | ferg | Platform: | |||
Assigned To: | ferg | OS: | |||
Priority: | normal | OS Version: | |||
Status: | closed | Product Version: | 4.0.11 | ||
Product Build: | Resolution: | fixed | |||
Projection: | none | ||||
ETA: | none | Fixed in Version: | 4.0.15 | ||
|
|||||
Summary: | 0004239: server returning 304 messages | ||||
Description: |
(rep by Jamison Novak) Here's what I see from the broken instance: [root@exertus log]# telnet 192.168.0.10 80 Trying 192.168.0.10... Connected to foo.com (192.168.0.10). Escape character is '^]'. GET /test/index.html HTTP/1.0 HTTP/1.0 304 Not Modified Server: Resin/4.0.11 ETag: "/qkrZAbHD5T" Last-Modified: Thu, 31 Dec 2009 17:32:15 GMT Accept-Ranges: bytes Cache-Control: max-age=5 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: <rewrite-real-path> <real-path regexp="^/test" target="/usr/local/www/test/wad"/> </rewrite-real-path> 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: | |||||
Additional Information: | |||||
Relationships | |||||
Attached Files: |
Notes | |||||
|
|||||
|
|