Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am seeing the issue in one of my web server access logs which is proxying to weblogic

...-0400] "GET /" 500 32

Can you suggest what this might mean. It is a sunone web server

share|improve this question
3  
Someone tried to access the root page for a domain, and got a 500 error. –  ceejayoz May 10 '12 at 20:40
add comment

2 Answers

up vote 0 down vote accepted

This means that the request failed with status code 500, which indicates that an error occurred in the server. It could have occurred in either SunOne or WebLogic, so you need to check the error logs of both to determine why it happened. (If SunOne encountered a network problem when communicating with WebLogic it should return a 502 or 504 status code, so this is an actual application error.)

share|improve this answer
add comment

as @ceejayoz said 500 indicates the error response code. 32 is the size of the response in bytes.

I generated an example log for the "common" format log entry that sunone uses by default;

127.0.0.1 - - [10/Ma...100] "GET /Bg.png HTTP/1.1" 200 2445 <--- correct formatted HTTP request
127.0.0.1 - - [10/Ma...100] "GET /" 200 11172   <--- HTTP/1.0 request

The example request is missing a HTTP/1.1 from the request line, so its an old style (HTTP/0.9 compatible) HTTP/1.0 request. So it unlikely to be a request from a browser. It could be a manual telnet request e.g. telnet localhost 80, or someone using wget/curl in HTTP/1.0 mode, or a http client library.

As @mgorven mentioned, its a server error, hence it is either being returned locally from the default virtual server (because thats where the HTTP/1.0 requests end up) or from the remote proxied server.

share|improve this answer
    
Thanks for your explanation, but would this be a 500 response from the web server to the source which was hitting, or a response that it got back from the server to which it was proxying to. –  brooding_goat May 10 '12 at 23:47
    
the docs for sunone are not that revealing, indicating just a Server error. You can still match up the time of the log entry to the log files on the proxy-target instance, or if this is happening frequently from some host XXX then you could use tcpdump -s0 -w /tmp/hostXXX host XXX to capture the requests and inspect them fully. –  Tom H May 11 '12 at 4:33
    
also, just try it and see. do telnet localhost 80 on the sunone server, and at the prompt type GET / and see what it puts in the logs –  Tom H May 11 '12 at 4:33
    
An badly formatted request should return status code 400, so unless SunOne has a bug in this regard this doesn't explain what is happening. –  mgorven May 13 '12 at 0:43
    
@mgorven hmm. i just checked the rfc and it seems that a GET / request is a valid HTTP/1.0 request. So point taken about "badly formatted requests" . –  Tom H May 13 '12 at 2:29
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.