Subject: | |
From: | |
Reply To: | |
Date: | Wed, 18 Oct 2000 08:02:00 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
HTTP 1.1 is described in RFC 2616
http://www.ietf.org/rfc/rfc2616.txt
See also http://www.w3.org/Protocols/
There's a tutorial at http://www.jmarshall.com/easy/http/
----- Original Message -----
From: "Andrew Cartledge" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Wednesday, October 18, 2000 7:49 AM
Subject: Programming a HTTP request (was posting to a URL)
> Good idea/Bad idea.
>
> This may be the triumph of hope over reality but can anyone identify any
> documents anywhere that explains, simply, the formatting requirements for
> headers when preparing to post to HTTP via port 80. I have found many on
> HTML formatting which discusses that the web application creates the
header
> data but nothing on how one would do it programatically.
>
> I notice from an earlier posting on this subject in May, C and Java
> libraries were referenced, but I would like to try do this 'manually', via
> a COBOL program of all things.
>
> I have established I can post data out on port 80 but cannot get to grips
> with the formatting requirements of the HTTP header.
>
> The XML layouts (for thats what I intend to send) are pretty straight
> forward and I understand the tag delimitation.
>
> Its establishing the initial contact and delimiting the header data.
>
> The idea is that I will open socket 80 and simply post the string of data
> off to the application within the web area.
>
> I am currently trying to test this, with a simple script, on my HP by
> posting to a URL within my Apache environment, although eventually it will
> be out on the network, and get the following error in my apache error_log;
>
> [Tue Oct 17 17:19:30 2000] [error] Invalid URI in request POST public-
> html/titlemnt.bin HTTP/1.0 Content-Length: 31
> titlecode=1&salut=MR&ACTION=ADD
>
> The value ' POST public-html/titlemnt.bin HTTP/1.0 Content-Length: 31
> titlecode=1&salut=MR&ACTION=ADD ' is that simply sent via an IPCSend out
on
> port 80 from a cobol prog.
>
> I may be asking a lot but, who knows, there could be something out there.
>
|
|
|