EldoS | Feel safer!

Software components for data protection, secure storage and transfer

Elhttpsclient : Invalid address (error code is 96260)

Also by EldoS: CallbackProcess
A component to control process creation and termination in Windows and .NET applications.
#14325
Posted: 08/31/2010 16:03:51
by Nagarajan KS (Priority Standard support level)
Joined: 08/09/2010
Posts: 4

I am using elhttpsclient for VCL.
Whenever I try to access a url with multiple parameters as given below,

httpsclient.Get('https://www.xyz.com/abcdef/register.php?username=mrnags&password=xyzxyz&password_confirmed=xyzxyz&email=mrnags@pqr.com');,

I am getting the below given exception..

First chance exception at $7C812AFB. Exception class EElSocketError with message 'Invalid address (error code is 96260)'. Process application.exe (560)

Can you help me?

Thanks
#14326
Posted: 08/31/2010 16:43:19
by Eugene Mayevski (EldoS Corp.)

In order to check the issue we need the exact URL from you. It can be a test URL, but we need to pass it to the parser in order to see what exactly goes wrong in parsing. If the URL is confidential, please post it to HelpDesk, which is a private communication channel between you and our developers.


Sincerely yours
Eugene Mayevski
#14390
Posted: 09/07/2010 03:18:19
by Nagarajan KS (Priority Standard support level)
Joined: 08/09/2010
Posts: 4

The issue is resolved.
When I used GET method and sent parameters via url, the url parser fails.
i.e suppose i send
Quote
https://www.xyz.com/abcdef/register.php?username=mrnags&password=xyzxyz&password_confirmed=xyzxyz&email=mrnags@pqr.com
, the url parser takes
Quote
https
as protocol,
Quote
.com
as the TLD,
Quote
www
as the subdomain and
Quote
xyz.com/abcdef/register.php?username=mrnags&password=xyzxyz&password_confirmed=xyzxyz&email=mrnags@pqr
as the domain name.

Therefore I am using POST instead of GET where the issue is not there.

Is that advisable?
#14391
Posted: 09/07/2010 03:39:25
by Eugene Mayevski (EldoS Corp.)

Most likely it's @ sign that confuses the parser. The rule of thumb is to hex-encode all non-alphanumeric symbols in URL parameters. I.e. @ should not be present in your URL in non-encoded form.


Sincerely yours
Eugene Mayevski

Reply

Statistics

Topic viewed 4180 times

Number of guests: 1, registered members: 0, in total hidden: 0




|

Back to top

As of July 15, 2016 EldoS Corporation will operate as a division of /n software inc. For more information, please read the announcement.

Got it!