asp.net to php

[hmm]

I want to create a process on asp.net that, by interaction on a .aspx page a
process is fired off that creates and sends a file via https: to a URL which
is a php page.

The php page will insure that the file is from an approved source, capture
it, and process it. (Because the source is only one particular web site,
perhaps it's safe to allow all from the source IP addr of the web site.)

Ideas on how to best accomplish this?

[RhythmAddict]

Could be wrong here - but...I don't think ASP.NET is going to
distinguish much between HTTP & HTTPS. You could probably work from
this article (http://aspnet.4guysfromrolla.com/articles/102605-1.aspx)
and focus on just creating the HTTP request if you haven't already.

Also a question, I'm confused on one thing...is this PHP page built or
do you have to build it? It's probably best to verify something other
than just the source IP, at least some basic file/size or a
checksum...shouldn't be too hard, but focus on the above, first.

[hmm]

I've not used the WebClient class or the HttpWebRequest class. I assume one
of these would be the tool to use for this?

"RhythmAddict" <sanjay...@gmail.com> wrote in message
news:6bd8a037-7e33-4d3c...@a1g2000hsb.googlegroups.com...

[NC]

On Apr 7, 11:36 am, "hmm" <nob...@nowhere.com> wrote:
>
> I want to create a process on asp.net that, by interaction on a .aspx
> page a process is fired off that creates and sends a file via https:
> to a URL which is a php page.

Why bother with the file? Just send raw data in a POST request...

> The php page will insure that the file is from an approved source,
> capture it, and process it. (Because the source is only one
> particular web site, perhaps it's safe to allow all from the source
> IP addr of the web site.)
>
> Ideas on how to best accomplish this?

On the requesting (ASP.Net) side, you will need to use HttpWebRequest
and HttpWebResponse classes:

http://msdn2.microsoft.com/en-us/library/system.net.httpwebrequest.aspx
http://msdn2.microsoft.com/en-us/library/system.net.httpwebresponse.aspx

On the responding (PHP) side, it's not going to be any different from
handling a form submission.

Cheers,
NC

[hmm]

Thanks.

"NC" <n...@iname.com> wrote in message
news:0a85d5b9-2f8e-4c92...@a5g2000prg.googlegroups.com...