ASP.Net App Issue... Maybe Resolved via PERL?
I have some classes that I recently built for a website which uses
HttpWebRequest & HttpWebResponse objects from the System.Net
Basically, the classes rap submitted data up, connect to external
on external servers and post / remove the data from these other sites.
It works fine locally but when uploaded to the BCentral production
the outgoing requests get shutdown.
Apparently, for the System.Net name space, you cannot specify the
outgoing port will be dynamic random. It will be the client port and
service port. The port range can be 1024 and above. It is by design
there is no way you can specify the client port.
Now, as for BCentral, they do allow outbound connections but only on
"default" ports such at 80 for http, etc. Every other non-essential
is locked down and they don't open up other ports because of security
I have been told that posting data via CGI is very common and that one
can easily specify the port. Has anyone out there done something like
Re: ASP.Net App Issue... Maybe Resolved via PERL?
[.. removed a bunch of stuff that has nothing to do with the question...]
> I have been told that posting data via CGI is very common and that one
> can easily specify the port. Has anyone out there done something like
No. No one has ever done anything with CGI.... My favorite search
engine doesn't find any hits for "perl cgi", I guess yours doesn't
|All times are GMT. The time now is 11:17 PM.|
Powered by vBulletin®. Copyright ©2000 - 2014, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.