First you get a clue. Then you read the HTML. You will either see the function pointed to by the onClick handler on the submit button or a tag(s) like <script language="javascript" src="/js/review.js"></script>

If you can't find something that says function WhateverItWasCalled you will need to get the included external javascript files and trawl through them. That is the review.js file in the example above.

Are there a way to find out what query string the registrar is using? You know, what type of textfield names, values, submit button names, values are required to submit the data for registration. It's a pain in the ass to go through each registrar's registration page, and do a view source.

Look you need to get with the program. Data can be sent by GET or POST or both. You may or may not need to send a session cookie or other session data. If it is HTTPS it is encrypted the moment it leaves your browser so you can't capture packets, if not you can. Some browsers let you look at what the browser is doing in more detail than say IE. Get a copy of Mizilla Firebird and have a look at Tools|Page Info which will show you all the forms and form fields and Tools|Options|Privacy|Cookies|View Cookies to see cookies including memory resident ones.

It's a pain in the ass to go through each registrar's registration page, and do a view source.

You are breaking my heart. That is likely what you will have to do most/all of the time. Every time they change their API you code will typically break as well BTW. Some registrars offer back end APIs.

cheers

tachyon

Haha, those sneaky sobs! I figured it out. I knew they had to use some sort of value to submit that particular page. Therefore, I looked for the value within that javascript button. Then searched for the same value within that registration page. Guess what I have found? The field name for that value. All I had to do next was pop in the name pertaining to that value. Bam, registration success.


But what I still need to do is get the io::socket::ssl to register the domain name. This works for LWP using useragent, but I'm still not good enough in PERL to implement LWP into my script that uses socket.


For some reason, when I run the script using IO::Socket::SSL, the values of the query string is posted. I notice it because I printed out the query. I didn't really change the script a whole lot.


Before it was IO::Socket::INET, now I changed it to IO::Socket:SSL.


It submits it using INET, but won't work with SSL. The website uses HTTPS, therefore, INET won't work. It needs SSL. But when I run the script, it just freezes when it prints out the query string. It shouldn't be any error with the SSL connection, if so, it would print out an error message to the text file.


Therefore, the problem must be within posting the data to the server for validation. How do you post data through IO::Socket:SSL? Is it the same as IO::Socket::INET?


This is how I post it with IO::Socket::INET.


$state{'username'} = $username;
$state{'username'} = $password;
[download]

username is the textfield name, $username is the variable that stores value. That in which is called from a external file that stores all the registration/personal info.


So is this how you would do it for posting data using IO::Socket::SSL or different? If so, what is the correct way? Thanks again for the help... Damn this is fun!

I gave you the exact code you need to use to POST using LWP::UserAgent. I also told you how to debug SSLsockets and suggested you don't know enough to be using them directly. You don't. Use LWP of read the fine RFCs, run debug level 4 and fix whatever the problem(s) are.

cheers

tachyon