RE: HTTP Headers -- WEB400

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Windows/DOS generally/sometimes sends 0x0D 0x0A (Carriage Return/Line Feed 
pair) for a new line.
Linux, on the other hand, just sends one of them (0x0D I *think*).  That may be 
why there are two of those boxes there (representing non displayable 
characters).

Or, it could in fact be two line feeds, hard to say without seeing the byte 
values.

Regards,

Jim Langston

-----Original Message-----
From: Brad Stone [mailto:brad@bvstools.com]
<SNIP>
> html</Name></URLAttachment></Email> HTTP/1.1Host:
> 99.99.99
> .99:8080

It looks like you have 2 newlines after HTTP/1.1 (I see two boxes on my 
display).  This could cause a problem as it will ignore or misinterprert the 
Host: portion of the header. Remember, 2 newlines means "I'm done!"  So make 
sure you don't have 2 somewhere.

The reason I think there are 2 after HTTP/1.1 is because if there are 2 after 
the Host parm, where I also see two boxes, I would assume there are 2 in the 
prior position as well causing an abnormal end in your case.  And if I recall 
from a previous inquiry, you needed the Host HTTP header for it to work.

Brad

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.