comment on

Thanks for th reply, but allowing redirection does not solve the problem. While Lynx get the next page - the Perl-program gets again the initial page.
Could it be that Lynx writes a coockie on the server, while Perl doesn't do that? Lynx is set that it does not accept any cookie - so no cookie is written on my computer.

This is from Lynx:

LYCookie: Searching for 'subscriber.chello.at:80', '/sms/index.php3'.
Composing Authorization for subscriber.chello.at:80/sms/index.php3
HTAASetup_lookup: No template matched `sms/index.php3' (so probably no
+t protected)
HTTP: Not sending authorization (yet).
Writing:
GET /sms/index.php3 HTTP/1.0
Host: subscriber.chello.at       ....
----------------------------------
HTTP Request is sent.
HTTP: WRITE delivered OK
HTTP Request sent; waiting for answer.
HTTP: Trying to read 1535
HTTP: Read 1448
HTTP: Rx: HTTP/1.1 200 OK
HTTP: Scanned 2 fields from line_buffer
--- Talking HTTP1.
HTTP/1.1 200 OK
....
Connection: close
[download]

this I got using Perl (I set in Perl the User-Agent to Lynx 2.8.4rel.1, it could be ...):

_protocol => HTTP/1.1
_request => HTTP::Request=HASH(0x84e226c)
_headers => HTTP::Headers=HASH(0x84e8fac)
_previous => HTTP::Response=HASH(0x84dfda0)
_msg => OK
_rc => 200
[download]

The content of the response (rc=200) is the initial web-page. It is not the next form to enter the sms text.

Here are the Information of Previous, Headers and Request:

Previous:
_protocol => HTTP/1.1
_request => HTTP::Request=HASH(0x84e22a8)
_headers => HTTP::Headers=HASH(0x84dfd94)
_rc => 302
_msg => Found
_content =>

Previous-Headers:
client-transfer-encoding => chunked
client-response-num => 1
location => /sms/index.php3
content-type => text/html
server => Apache/1.3.26 (Unix) PHP/4.2.1
connection => close
date => Tue, 06 Aug 2002 09:28:00 GMT
x-powered-by => PHP/4.2.1
client-date => Tue, 06 Aug 2002 09:28:00 GMT

Previous-Request:
_method => POST
_headers => HTTP::Headers=HASH(0x84e229c)
_uri => http://subscriber.chello.at/sms/austria.php3
_content => austria=43699&image.x=0&image.y=0

Previous-Request-Headers:
user-agent => Lynx/2.8.4rel.1
content-type => application/x-www-form-urlencoded
content-length => 33
   - - - - - - 

Request:
_method => POST
_headers => HTTP::Headers=HASH(0x84dfaac)
_uri => http://subscriber.chello.at/sms/index.php3
_content => austria=43699&image.x=0&image.y=0

Request-Headers:
user-agent => Lynx/2.8.4rel.1
content-type => application/x-www-form-urlencoded
content-length => 33

  - - - - - -

Headers:
client-transfer-encoding => chunked
client-response-num => 1
title => hello, i'm chello
content-type => text/html
server => Apache/1.3.26 (Unix) PHP/4.2.1
x-meta-author => chello broadband B.V 1999
date => Tue, 06 Aug 2002 09:28:05 GMT
connection => close
x-powered-by => PHP/4.2.1
link => </dhtml/style/sliding.css>; rel="stylesheet"; type="text/css"
client-date => Tue, 06 Aug 2002 09:28:10 GMT
[download]

In reply to Re: Re: submit Form with Lynx but not Perl? by Anonymous Monk
in thread submit Form with Lynx but not Perl? by Anonymous Monk

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.