abrooks3640
Technical User
- Nov 1, 2012
- 16
I am currently running a pre-packaged (off-the-shelf) file delivery service that runs within a web browser. This service has it's Web Interface set to operate on port 8080.
For branding of this service (and for internal adjustment of user credentials) I am also running Apache 2 with PHP 5.6 on the same machine. The Apache server is running on 80 and the file delivery service is appears inside an iframe of the Apache's homepage.
I've had very good luck with all most all users of this except a few inside corporations running tighter firewalls. The claim from one of the IT person at one of those places is that because the 8080 request is coming not from one of his internal machines but, essentially, from my PHP page with the iframe, his firewall is denying access to the server running 8080.
I'm not sure about this. And if this is the case, how could his client computers see any videos (instructional, perhaps) on webpages with youtube iframe code? Wouldn't that be the same thing?
Also, what he describes basically sounds like the way any NAT router works except all those I am aware of are smart enough to make this type of thing work.
It's my opinion that it's an issue with running a web server on a (slightly) non-standard port of 8080. I've asked whether they can access the iframed server by direct access (i.e..: and have received contradictory answers.
MORE INFO: Since both servers are running on the same machine, I don't think it's not a question of cross site issues. Both servers are within the same domain name and server name. The only difference is the port.
My main question is: What is truly initiating the 8080 request in this situation? Is it his client machine or is it my PHP script?
Any help or insight on this would be greatly appreciated.
For branding of this service (and for internal adjustment of user credentials) I am also running Apache 2 with PHP 5.6 on the same machine. The Apache server is running on 80 and the file delivery service is appears inside an iframe of the Apache's homepage.
I've had very good luck with all most all users of this except a few inside corporations running tighter firewalls. The claim from one of the IT person at one of those places is that because the 8080 request is coming not from one of his internal machines but, essentially, from my PHP page with the iframe, his firewall is denying access to the server running 8080.
I'm not sure about this. And if this is the case, how could his client computers see any videos (instructional, perhaps) on webpages with youtube iframe code? Wouldn't that be the same thing?
Also, what he describes basically sounds like the way any NAT router works except all those I am aware of are smart enough to make this type of thing work.
It's my opinion that it's an issue with running a web server on a (slightly) non-standard port of 8080. I've asked whether they can access the iframed server by direct access (i.e..: and have received contradictory answers.
MORE INFO: Since both servers are running on the same machine, I don't think it's not a question of cross site issues. Both servers are within the same domain name and server name. The only difference is the port.
My main question is: What is truly initiating the 8080 request in this situation? Is it his client machine or is it my PHP script?
Any help or insight on this would be greatly appreciated.