Writing into the Pickup directory

I did not specify the language, but the code is VBScript.
I tried using .Item, but it's the same...
The C++ component I'm using is not to avoid CDOSYS, it is to send data
to an ASP page. On server side, the ASP page can use CDOSYS or write
directly into the Pickup directory as I'm doing. I repeat that the
problem is not sending the email message, because it's working, but
it's in receiving data. Using a PHP script it's receiving data, but
the ASP script it's not receiving data...

"carmelo" <csaffi@tiscali.it> wrote in message
news:61ce46f0-e8f8-4cc9-9369-7253dfaa4098@8g2000hse.googlegroups.com...
> I did not specify the language, but the code is VBScript.
> I tried using .Item, but it's the same...
> The C++ component I'm using is not to avoid CDOSYS, it is to send data
> to an ASP page. On server side, the ASP page can use CDOSYS or write
> directly into the Pickup directory as I'm doing. I repeat that the
> problem is not sending the email message, because it's working, but
> it's in receiving data. Using a PHP script it's receiving data, but
> the ASP script it's not receiving data...

K the penny has dropped, the C++ code is running client-side.

At a guess I suspect the client side component is not setting the request
content type properly.

The Content-Type header should be set to application/x-www-form-urlencoded


--
Anthony Jones - MVP ASP/ASP.NET

"Anthony Jones" <Ant@yadayadayada.com> wrote in message
news:OipbOpz3IHA.3500@TK2MSFTNGP05.phx.gbl...
> "carmelo" <csaffi@tiscali.it> wrote in message
> news:61ce46f0-e8f8-4cc9-9369-7253dfaa4098@8g2000hse.googlegroups.com...
> > I did not specify the language, but the code is VBScript.
> > I tried using .Item, but it's the same...
> > The C++ component I'm using is not to avoid CDOSYS, it is to send data
> > to an ASP page. On server side, the ASP page can use CDOSYS or write
> > directly into the Pickup directory as I'm doing. I repeat that the
> > problem is not sending the email message, because it's working, but
> > it's in receiving data. Using a PHP script it's receiving data, but
> > the ASP script it's not receiving data...
>
> K the penny has dropped, the C++ code is running client-side.
>
> At a guess I suspect the client side component is not setting the request
> content type properly.
>
> The Content-Type header should be set to application/x-www-form-urlencoded
>
>


I just noticed in the C++ that the component you are using is called
TIdMultiPartFormDataStream. This would indicate its using the content type
multipart/form-data in order to simulate the sending of a file. ASP does
not support this content type natively.

--
Anthony Jones - MVP ASP/ASP.NET

> > K the penny has dropped, the C++ code is running client-side.
>
> > At a guess I suspect the client side component is not setting the request
> > content type properly.
>
> > The Content-Type header should be set to application/x-www-form-urlencoded
>
> I just noticed in the C++ that the component you are using is called
> TIdMultiPartFormDataStream. *This would indicate its using the content type
> multipart/form-data in order to simulate the sending of a file. *ASP does
> not support this content type natively.

What do you suggest to avoid this problem?

I hope in your help
Carmelo

"carmelo" <csaffi@tiscali.it> wrote in message
news:ae3965c1-b0c2-4c47-8af7-2da48386502e@e53g2000hsa.googlegroups.com...
>> > K the penny has dropped, the C++ code is running client-side.
>>
>> > At a guess I suspect the client side component is not setting the
request
>> > content type properly.
>>
>> > The Content-Type header should be set to
application/x-www-form-urlencoded
>>
>> I just noticed in the C++ that the component you are using is called
>> TIdMultiPartFormDataStream. This would indicate its using the content
type
>> multipart/form-data in order to simulate the sending of a file. ASP does
>> not support this content type natively.
>
>What do you suggest to avoid this problem?
>

Use something that posts with the application/x-www-form-urlencoded content
type instead of multipart/form-data.


--
Anthony Jones - MVP ASP/ASP.NET

carmelo wrote on Mon, 7 Jul 2008 01:00:23 -0700 (PDT):

>>> K the penny has dropped, the C++ code is running client-side.

>>> At a guess I suspect the client side component is not setting the
>>> request content type properly.

>>> The Content-Type header should be set to
>>> application/x-www-form-urlencoded

>> I just noticed in the C++ that the component you are using is called
>> TIdMultiPartFormDataStream. This would indicate its using the
>> content type multipart/form-data in order to simulate the sending of
>> a file. ASP does not support this content type natively.

> What do you suggest to avoid this problem?

As Anthony suggests you could change the client to use
application/x-www-form-urlencoded . If you cannot change the client, then
you could use some code on the server to handle this content type and decode
it for you. There are various components and scripts that can do this -
check with the server admin to see if any "upload" components are installed
(eg ASPUpload) and if you can use one of these, it should allow you to
access the Form values after decoding. If there are no "upload" components
installed, and you need a pure code solution, look at
ttp://www.motobit.com/help/scptutl/pure-asp-upload.htm - this is a class
that you can use that is pure ASP, and will do the decoding for you.

--
Dan

Ok, now I was able to post data.
But it seems that the message length is limited, so I'm not able to
post long text data...

What do you suggest?


Thank you again
Carmelo

"carmelo" <csaffi@tiscali.it> wrote in message
news:53e92966-bf1f-41fb-a18c-8310e61934fa@x35g2000hsb.googlegroups.com...
> Ok, now I was able to post data.
> But it seems that the message length is limited, so I'm not able to
> post long text data...
>
> What do you suggest?

How do you know it limited?
How big is the data you are posting?

The default max entity body on IIS6 is 200K however if your site is hosted
by a third party then it may be different.

--
Anthony Jones - MVP ASP/ASP.NET

I made some tests and I discovered that the limit was not due to IIS
but to the presence in the message of the "&" character... now that I
handled it, it works...