 |
tonyp
New User
Nov 13, 2008, 12:38 PM
Post #1 of 4
(688 views)
Shortcut
|
|
search issue / nonstandard port
|
Can't Post
|
|
Our server is behind a NAT firewall where it is redirected to a nonstandard port number. Externally, it is port 80 but internally it is 82. We are getting the following error when we try to search:
Error: Can't connect to '<external hostname>.' (<external IP>) on port 80 : Connection timed out at
/artman2/cgi-bin/modules//IT/SSIResolver.pm line 362.
The server does support SSI and we have control over the firewall. What do we need to do to make searches work? I've tried aliasing the server's external hostname to localhost but that didn't work (presumably because the port was still different). We'd rather not use emulated SSI if it slows the site down at all. Is it not possible to just configure Article Manager with the internal IP and port for searches? I tried changing the Search URL in the Server Settings to use <internal_IP>:<internal port> but that didn't help.
|
|
| |
|
Donna
Staff
/ Moderator
Nov 14, 2008, 4:01 PM
Post #2 of 4
(678 views)
Shortcut
|
|
Re: [tonyp] search issue / nonstandard port
[In reply to]
|
Can't Post
|
|
Hi Tony,
Emulated SSI won't slow anything down at all -- but it will keep you from running dynamic scripts (ie, PHP) in your dynamic search pages. If that's not an issue, feel free to switch to emulated SSI.
If you're using PHP or other dynamic scripts on your search pages, let me know and I'll see what I can come up with... :)
Donna
Hire me!
Save time by getting our experts to help with your project. Template changes, advanced features, full integration, whatever you need. Whether you need one hour or fifty, get it done fast with Priority Consulting.
|
|
| |
|
tonyp
New User
Nov 19, 2008, 8:52 AM
Post #3 of 4
(654 views)
Shortcut
|
|
Re: [Donna] search issue / nonstandard port
[In reply to]
|
Can't Post
|
|
Hi Donna,
Sorry for taking so long to reply. I heard back from our web developer and he said that he will need to have dynamic content on search pages.
As a test, I tried hardcoding "localhost" and port 82 into SSIResover.pm and it did work. Of course, we'd rather see a supported solution, such as putting these values into a config file (feature request!).
Please let us know if there's a better way around this.
Thanks,
Tony
|
|
| |
|
Dave
Staff
/ Moderator
Nov 20, 2008, 1:16 PM
Post #4 of 4
(640 views)
Shortcut
|
|
Re: [tonyp] search issue / nonstandard port
[In reply to]
|
Can't Post
|
|
Hi Tony,
Hardcoding it is probably the best way for now.
I believe it uses the publish url by default to get the hostname from. So you might also be able to make it work by changing that (but then your other links would have port 82) or hardcoding it in /modules/IT/App/Init.pm. (Search for 'SERVER_RESOLVED_SSI_TEMPDIR_URL'). But, if it's working now I'd just make a note of the change and leave it for now.
Dave Edis - Senior Developer
interactivetools.com
|
|
| |
|
