🚀 go-pugleaf

Jan wrote:

> I try to post a XML file but get always the error:
> Invalid argument to data encode.

What component are you using ?
On which statement do you get the error ?
Do you get the error in the catch block ?

>       TStringList *LIpost = new TStringList;

>           HTTP->Post(PathHttp, LIpost);

Well you are trying to post -the contents of- a TStringList.

> And here the XML file:
> 
> <schemainstances><schemainstance id="2851" schemamnemonic="product">
....
> </schemainstance></schemainstances>

Please first try to post a file or TStringList that only has a line
of five and does not contain CDATA. Is that possible ? Is it
only whith this specific file ?

Hans.

Hans Galema wrote:

> What component are you using ?
> On which statement do you get the error ?
I use Indy version 9.00.10 and BCB 5

> Do you get the error in the catch block ?
No, on the Post method

> 
> >      TStringList *LIpost = new TStringList;
> 
> >          HTTP->Post(PathHttp, LIpost);
> 
> Well you are trying to post -the contents of- a TStringList.
> 
> 
> Please first try to post a file or TStringList that only has a line
> of five and does not contain CDATA. Is that possible ? Is it
> only whith this specific file ?
> 
I have try with a small XML file without CDATA and get thesame error.

I don't think I need to pass a parameter list to the HTTP.
The URL is quite normal:
http://192.168.2.191/synchronize/schemainstance_import.aspx and runs
now on a locat test webserver with the latest .Net framework.

I have also try with a Stream, but no difference.
String PathHttp =
"http://192.168.2.191/synchronize/schemainstance_import.aspx";
TMemoryStream *Astream = new TMemoryStream();
Astream->Clear();
Astream->LoadFromFile("C:\\Temp\\Test.xml");
HTTP->Post(PathHttp, Astream);

And the Test.Xml :

<schemainstances><schemainstance id="2851" schemamnemonic="product">
  <createdts>05/07/2005 01:46:04 PM</createdts>
		<name>CAMBQQA6D1A</name>
		<locales>
			<locale name="common">
					<foto>
					 <value>Q3702A_190X170.JPG</value>
					</foto>
					<category>
							<value>BQ</value>
					</category>
					<frontpage>
							<value>True</value>
					</frontpage>
					<price>
							<value>0</value>
					</price>
			</locale>
			<locale name="nl-be">
					<title>
							<value>Camera BenQ DC E40 4.0M GOLD</value>
					</title>
			</locale>
	</locales>
</schemainstance></schemainstances>

Jan wrote:

>>What component are you using ?

> I use Indy version 9.00.10 and BCB 5

That is a componentsuite which contains many components.
Which do you use here ?

>>Do you get the error in the catch block ?
> 
> No, on the Post method

> I don't think I need to pass a parameter list to the HTTP.

What do you mean with that ?

> The URL is quite normal:
> http://192.168.2.191/synchronize/schemainstance_import.aspx and 

If your error is: "Invalid argument to data encode." then the Post
is probably not done then the URL is not used. Try a non existing URL
and see what happens.

So there is no exeption thrown by Post on that error and ShowMessage()
in  your code is not invoked ? Is there a return-value for the Post
method that you have to consider ?

You could also tell if this are your first steps with
this component or that you used Post() a lot without problems
on other URL's.

Hans.

"Jan" <jan@jlcsoft.com> wrote in message
news:42ca6485@newsgroups.borland.com...

>       HTTP->Response->ContentType = "text/xml";

You should be filling in the Request, not the Response.

>       HTTP->Connect(IdTimeoutDefault);
>       if (HTTP->Connected())  {

This is not the cause of the problem, but you should get rid of that code.
You are not supposed to be doing that.  Post() handles that internally.

>         LIpost->LoadFromFile(sSourceFile);

Rather than using a TStringList, use a TFileStream instead.  Indy does extra
processing on TStrings parameters but not on TStream.  Your XML is going to
get potentially messed up during the Post() if you use a TStringList.

Use this code instead:

    TFileStream *LIpost;
    try
    {
        LIpost = new TFileStream("C:\\Temp\\test.xml", fmOpenRead |
fmShareDenyWrite);
        try
        {
            HTTP->Request->ContentType = "text/xml";
            HTTP->Post(PathHttp, LIpost);
        }
        __finally {
            delete LIpost;
        }
    }
    catch(const Exception &e)
    {
        ShowMessage("Error encountered during POST: " + e.Message);
    }


Gambit

"Jan" <jan@jlcsoft.com> wrote in message
news:42ca75b0@newsgroups.borland.com...

> I have try with a small XML file without CDATA and get thesame error.

The content of the XML is irrelavent.  Indy does not process it.

> I have also try with a Stream, but no difference.

Using a stream is exactly what you should be doing.


Gambit

"Hans Galema" <notused@notused.nl> wrote in message
news:42ca90d2$1@newsgroups.borland.com...

> That is a componentsuite which contains many components.
> Which do you use here ?

There is only one HTTP client component in Indy - TIdHTTP.  If you don't
know how Indy works, then you should not be answering Indy-related
questions.


Gambit

"Jan" <jan@jlcsoft.com> wrote in message
news:42ca6485@newsgroups.borland.com...

> I try to post a XML file but get always the error:
> Invalid argument to data encode.

There is no such error message in Indy, or the VCL in general for that
matter.  Are you sure that the error message isn't actually the following
instead?

    Invalid argument to date encode.

Notice *date* vs. *data*.

What is the actual class type, not the text message, of the exception being
thrown?

    catch(const Exception &e)
    {
        ShowMessage(e.ClassName());
    }

If the error is actually an invalid *date* encoding, then that suggests that
either:

1) you did not specify a valid Request->Date, Request->Expires, or
Request->LastModified value

2) the server sent back a Response->Date, Response->Expires, or
Response->LastModified value that Indy does not understand.

Those are the only date-related values that TIdHTTP uses.


Gambit

Remy Lebeau (TeamB) wrote:

> There is only one HTTP client component in Indy - TIdHTTP.  

Yes. I know. No reason for the OP not to name it. Especially
when asked.

 > If you don't
> know how Indy works, then you should not be answering Indy-related
> questions.

Please do not chase away people that try to help others. I had already
looked at a HTTPCLient example and was amazed that Jan used Response.
Besides, there is much more in the OP's post then Indy. Until now I
had more questions for the OP then answers. That is my way to help the
OP to formulate/understand a problem.

Even if I had never heard of Indy then still all the remarks and
questions I made in this thread were adequate.

Why do you condemn so fast? Let others live.

Hans.

> There is no such error message in Indy, or the VCL in general for that
> matter.  Are you sure that the error message isn't actually the
> following instead?
> 
>     Invalid argument to date encode.
> 
> Notice date vs. data.
Yes, sorry, it is DATE

> 
> What is the actual class type, not the text message, of the exception
> being thrown?
> 
>     catch(const Exception &e)
>     {
>         ShowMessage(e.ClassName());
>     }
> 
The code don 't execute the catch statement, on the post methode, 0.5
seconds later I get the error.

> If the error is actually an invalid date encoding, then that suggests
> that either:
> 
> 1) you did not specify a valid Request->Date, Request->Expires, or
> Request->LastModified value
Gives nothing when I change this values.
> 
> 2) the server sent back a Response->Date, Response->Expires, or
> Response->LastModified value that Indy does not understand.

Can it be that it is a aspx page .Net framework ?
I check tomorrow with the network administrator for the settings on the
webserver.

Thanks for the tip and help.

Jan

"Jan" <jan@jlcsoft.com> wrote in message
news:42caf232@newsgroups.borland.com...

> The code don 't execute the catch statement

The only way that can happen is if you are running your program inside the
IDE debugger, and the debugger is catching the exception before your code
does, displaying a popup message to you, and then when you dismiss the
dielog the exception is passed back to your code but Indy then traps the
exception internally and discards it so that your code never sees it.

Are you actually running your program inside the debugger?  What happens if
you run the program outside the debugger?


Gambit

Problem solved.
In the configuration of the .NET page I have removed the line
"trace=true" and works fine now. I think Indy have a problem with that.

Verry stranges.

Thanks for the help.

Jan