|Dart Home | PowerWEB File Upload for ASP.NET | Custom Development||Reply | PowerWEB File Upload for ASP.NET Topics | Forums|
|Author||Forum: PowerWEB File Upload for ASP.NET|
Topic: Operation with a hardware load balancer.
From: West Malling, Kent, United Kingdom
Member Since: 08/19/11
|posted August 19, 2011 7:08 AM
Dear sir or madam,
Re: "Flash Object reported an I/O error attempting to upload a file"
After running further Wireshark traces it is clear that our scenario is as follows:
1) Our 'Rackspace' hosted hardware 'TLS terminating' load balancer relays HTTPS (port 443) packets on to listening port 81 on our hosted WWW servers.
2) When the File Uploader function is undertaken from the client browser ir makes an attempt to establish a new connection with the load balancer at port 81 i.e. the web server's port rather than the port that gets relayed on by the load balancer to the web server (port 443).
3) When the load balancer is configured to merely relay on HTTP/port 80 packets directly to port 80 on the WWW servers then your company's File Uploader works fine and the Wireshark confirms that there are no issues! [The web server's own listening port being valid in this case.]
In short - can the client's attempted usage of the WWW server's listening port (rather than the load balancer's) be prevented by a configuration change? We already have 126.96.36.199 and so I suspect that an upgrade is not possible.
|Jamie Powell (Admin)
From: Rome, NY USA
Member Since: 03/13/07
Extra Support Options
Custom Application Development
|posted August 19, 2011 10:53 AM
Thank you for your post. This issue has been responded to off line. Please check your email for additional information.
|Reply | PowerWEB File Upload for ASP.NET Topics | Forums|
|This site is powered by PowerTCP WebServer for ActiveX|