Re: Re: Re: Re: How?

I know you gave me the exact codes. That wasn't the problem. I already written a script in LWP to register the domain with that registrar. But I was having that problem with the javascript button, which I have resolved and it could register domain names now.

But I'm trying to say that I don't know how to implement the script that uses LWP to register domain names with the script that register domains with sockets. That script checks if the domain is register or not then it register. Therefore, the function of the registration script from the socket is different from LWP.

That is why I prefer doing it with sockets as everything has been written to support sockets. I have done what you said by using debug 4. But it's given me all these junk which I don't understand what it is or how to use it to debug the script. Below is what printed after running script with debug 4.

got `HTTP/1.1 200 OK
(17:0 bytes, VM=vm_unknown)
got `Date: Mon, 01 Mar 2004 01:41:50 GMT
(37:0 bytes, VM=vm_unknown)
got `Server: Apache/2.0.47 (Unix) mod_ssl/2.0.47
OpenSSL/0.9.7b mod_jk/1.2.2
(73:0 bytes, VM=vm_unknown)
got `Set-Cookie:
JSESSIONID=07F7FEAF3E49D02951BACF23E700D181; Path=/website;
Secure
(80:0 bytes, VM=vm_unknown)
got `Content-Length: 4493
(22:0 bytes, VM=vm_unknown)
got `Connection: close
(19:0 bytes, VM=vm_unknown)
got `Content-Type: text/html;charset=ISO-8859-1
(44:0 bytes, VM=vm_unknown)
got `(2:0 bytes, VM=vm_unknown)
got `' (0:0 bytes, VM=vm_unknown)
got `' (0:0 bytes, VM=vm_unknown)
got `' (0:0 bytes, VM=vm_unknown)

Comment on Re: Re: Re: Re: How?

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: How? by tachyon (Chancellor) on Mar 01, 2004 at 12:51 UTC
Your IO::Socket::SSL, OpenSSL, Crypt::SSLeay, Firewall, Proxy, or other widget appear to have issues. Essentially you are making the SSL conn, then getting told to expect 4493 bytes of content BUT get nothing after the Content-Type Header. It could be all sorts of things. But you have a problem. You really have very little idea of what you are doing. You don't really understand the protocols you are trying to use and manipulate via sockets, nor how to read the debug output. You want to ignore the LWP module (which does generally just work cause its author did know what they were doing) and justify it that you already have code that uses sockets. I'll give you a hint. Your code as presented looks like spagetti. It would benefit from a rewrite to use LWP and all your problems will go away. Although you have some code it does not work. It does not scale. It is not easy to maintain. Get it? Do yourself a favour and use LWP. If that means rewriting your 'app' then that is what you should do. I have nothing more to add so don't bother replying. cheers tachyon	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Re: Re: How?
by tachyon (Chancellor) on Mar 01, 2004 at 12:51 UTC

Your IO::Socket::SSL, OpenSSL, Crypt::SSLeay, Firewall, Proxy, or other widget appear to have issues. Essentially you are making the SSL conn, then getting told to expect 4493 bytes of content BUT get nothing after the Content-Type Header.

It could be all sorts of things. But you have a problem. You really have very little idea of what you are doing. You don't really understand the protocols you are trying to use and manipulate via sockets, nor how to read the debug output. You want to ignore the LWP module (which does generally just work cause its author did know what they were doing) and justify it that you already have code that uses sockets. I'll give you a hint. Your code as presented looks like spagetti. It would benefit from a rewrite to use LWP and all your problems will go away. Although you have some code it does not work. It does not scale. It is not easy to maintain. Get it?

Do yourself a favour and use LWP. If that means rewriting your 'app' then that is what you should do. I have nothing more to add so don't bother replying.

cheers

tachyon

[reply]