|
Is there a way to not require the port from being required in the url when calling the cgi program?
The port has to be specified _somewhere_. Otherwise, the browser won't know which port to connect to. When the browser isn't told specifically which port to connect to, it connects to port 80.
However, you could have only one link to get you started, and then use relative links for the rest. That way, you'd only have to specify the custom port number once.
Is this an apache directive issue?
No, and if you think about it, you'll see why it can't be an Apache directive. It's the browser (not the HTTP server) that has to establish the connection. It has to know where Apache is -- which port -- in order
to connect to it.You can re-configure the server all day, it won't tell the browser to connect to it!
Putting the port number in the Apache config would be like me writing my own telephone number on my hand. Sure, I'd know my number whenever I needed it. But that wouldn't help YOU call me.
I've been looking through the examples and haven't been able to figure out how to not require the port. The reason I ask is that I see in some of my examples that don't use port 80, that the configured port is not specified.
They probably used relative links, which frankly, is the way to go.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
