Note that with Ovids solution you *may* have to parse out and include some or all of the hidden fields in the form as well as adding the user/pass fields, otherwise the login may fail.

Additionally the login STATE may be maintained by hidden fields in subsequent pages (you need to parse them out and add them into subsequent post login requests) or a SESSION COOKIE which you need to accept, save and pass with each post login request.

They forgot to specify the type for the UserID input box

You don't have to, the practical default is text

If you think about the transaction there is no data passed from browser to server about the type of field so provided the browser will render it you have no issue in the real world.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

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

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