By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
"HTTP/1.1 200 OK Server: Microsoft-IIS/5.0 Date: Fri, 04 Oct 2002 12:52:23 GMT Connection: close Content-Type: text/html;charset=ISO-8859-1 Servlet-Engine: Tomcat Web Server/3.2.3 (JSP 1.1; Servlet 2.2; Java 1.3.1_01; Windows 2000 5.0 x86; java.vendor=Sun Microsystems Inc.)"
Your error is in actuality the Status-line and response header of the HTTP message that your browser received. HTTP uses text headers to pass information about request and response messages. Each header consists of a list of unordered fields containing a field name and a field value delimited by a colon and a space. The Status-Line consists of the HTTP-protocol version followed by a status code and an a status phrase. The first digit of the status code defines the response class.
A breakdown of the Status-line and response header is as follows:
Header Name Header Value ============================================================ Status-Line: HTTP/1.1 200 OK Server: Microsoft-IIS/5.0 Date: Fri, 04 Oct 2002 12:52:23 GMT Connection: close Content-Type: text/html;charset=ISO-8859-1 Servlet-Engine: Tomcat Web Server/3.2.3 (JSP 1.1; Servlet 2.2;A rough translation of these fields is as follows:
Java 1.3.1_01; Windows 2000 5.0 x86; java.vendor=Sun
The Status-Line acknowledges that the responding server understands HTTP/1.1 and that it was able to handle the request successfully (status code = 200 and status phrase = OK).
The Server field indicates that the responding server is IIS, version 5.0.
The Date field indicates the date and time that the response was originated.
The Connection field indicates that the connection will be closed after completion of the response.
The Content-Type field indicates that the response body content-type is text/html and the media-type consists of character set ISO-8859-1.
The Servlet-Engine field indicates that the Web server is Tomcat, version 3.2.3. It also acknowledges additional information pertaining to other engines, JVM, OS, etc. that the Web server is using.
The question is: why are you receiving the response header as the content page?
Without seeing the source code for the JSP page, I can only offer a couple of possibilities:
1) The JSP page is explicitly trying to set the HTTP headers. Since a JSP/servlet handles this automatically any attempts to manually set them could result in them being handled as page content.
2) A blank line after the headers is the delimiter separating the headers from the page content. Try looking at the raw output of the response message to see if there is a blank line after the headers.
Dig Deeper on Microservices pattern, platforms and frameworks
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.