URL parsing problem (wodSFTP / wodSFTP.NET / wodSFTPdll)

Hi,

I am having a problem with TwodWebServerCom parsing a URL incorrectly.

This problem occurs when the URL is passing a variable value that is itself a URL.

for example if you type this URL into a browser:
[code]
http://dev-007xp/Go_Here?SomePath=http://dev-007xp/Not_here
[/code]
I see the same URL in the debug log, however by the time it arrives at the OnRequestHeaders event it has changed into
[code]
http://dev-007xp/Not_here
[/code]
It appears that the code withing the Server that processes the URL and chops it up into its various parts is getting confused and taking the 2nd URL by mistake.

I have a C++ builder 6 project that shows the fault. But I imagine it will happen under any environment.

Thanks
Paul

Paul,

yes, this was a bug, I was able to duplicate it. Fixed. Please request update!

Regards,
Kreso

Hi,

Thats fixed it up great.

Thanks again for the amazingly fast turn around.

Regards
Paul.

I have a somewhat similar issue:

This item:
<input name= trccvs value= <I>miscellaneous Text</I> >
is being parsed into:
<input name= trccvs value= <I>
and:
miscellaneous Text</I> >

Apparently due to the closing '>'.

Any chance this is already fixed in an update?

Hi Thomas,

I cannot duplicate it so probably it's fixed.

Please download latest 1.3.4.257 version from our website and let us know how it goes.

Regards,
Drazen

Hi Thomas,

I cannot duplicate it so probably it's fixed.

Please download latest 1.3.4.257 version from our website and let us know how it goes.

Regards,
Drazen

Well I updated HTML Parser to 1.0.0.9 (from .8) to no avail.

Here's the code I'm using and the result I'm getting:

Entity in lcFile html: <input name= trccvs value= <I>misc Text</I> >

loX = CREATEOBJECT( WeOnlyDo.wodHtmlParser.1 )
loX.load(lcFile)
loY = loX.parts.filter( input ).Search(ByAttributeValue, trccvs )
lcText = loY.item(0).attributes.item( value ).value
loX.unload()

Writing out lcText I get just: <I

Thomas,

I believe this should be fixed now. Please try updating to the latest version of wodHTMLParser and try it out.

Regards,
Damba

Thomas,

I believe this should be fixed now. Please try updating to the latest version of wodHTMLParser and try it out.

Regards,
Damba

That did it - thanks!