[5025] in WWW Security List Archive
Somewhat off-topic question...
daemon@ATHENA.MIT.EDU (hdemel@rbcds.com)
Thu Apr 10 22:16:00 1997
Date: Thu, 10 Apr 1997 18:39:32 GMT
From: <hdemel@rbcds.com>
To: www-security@ns2.rutgers.edu
Errors-To: owner-www-security@ns2.rutgers.edu
TO: www-security@ns2.rutgers.edu
All -
This is sort of a reverse-security issue of which I hope some of you could
give me a solution. I'm looking to change a phone-line-based solution to a
non-encrypted-Internet solution. I suppose it's not really a security
issue, but I'm using the 'reverse-security' thing as an excuse to tap some
knowledgable brains for an answer.
Currently, we use a home-grown web-based front end pager-sending program
which dials up our pager provider via an 800 number and sends pages. The
paging provider also offers web-based paging via a form page, but they use
POST as the method to submit to their form, and they don't support GET. If
they supported GET, I would just put the pager ID and message on the URL and
connect to their site autonomously. I don't know how to do this using POST.
My guess is I'd have to set variables like REQUEST_METHOD and
CONTENT_LENGTH, and somehow open a socket and send STDIN to them, or
something. There's where I get confused; I don't know how to do it
(variable setting and passing and piping STDIN to them).
Any ideas (Perl-based?) would be extremely appreciated.
Thx,
Harris Demel
