Main
Index 		Search
Posts 		Who's
Online 		Log
In

Home: Discontinued/Classic Products: Article Manager 2:
Issue with HTTP to HTTPS using Article Manager

 
 


troys
New User

Mar 27, 2009, 8:17 AM

Post #1 of 2 (1865 views)
Shortcut
Issue with HTTP to HTTPS using Article Manager Can't Post
Our college recently setup our main web site on IIS to be redirected to an HTTPS connection. We are using Article Manager 2 for our news articles (love it by the wayWink). The redirect works great so that any page accessed on our site will be a secure https connection. However, the only area that does not work is when you click next from the Article Manager index page or if you try to use the search. I did change the server settings in the AM admin console to have a https at the beginning of the search URL as well as the other URLs and republished all the articles. However when you try to use anything in Article Manager that uses search.cgi...it throws an error message saying:

[Server Resolved SSI Error : Server returned a response code of '302' on the following request:

Because of this I directed our main site back to http until I can get this resolved. The strange thing is that the search.cgi page works fine using http and if you manually type in the full URL with an https it works fine as well:

https://www.gdn.edu/scripts/artman2/search.cgi

Or if you click on NEXT from the main (global) index page and then add an "s" after http it shows the results just fine as well. I was wondering what I might could do to get the search to work in an HTTPS redirected site. Any ideas??

Is it something I need to change in the code for the search.cgi script?

Another strange thing is that the Admin console works just fine using the HTTPS redirect as well.


Donna
Staff / Moderator


Mar 31, 2009, 11:44 AM

Post #2 of 2 (1821 views)
Shortcut
Re: [troys] Issue with HTTP to HTTPS using Article Manager [In reply to] Can't Post
Hi there,

Article Manager uses a method of resolving dynamic code via the search engine by default that doesn't appear to be compatible with 302 redirects. What it's basically doing is creating temp file on your server, then reading it back into the program so that SSI's, PHP, and any other dynamic code you have is executed by the server. In your case, since there's a redirect, this interrupts the dynamic processing.

There are a couple of options: If you're using only SSI's, you can switch it to emulated SSI's. However, if you're using PHP or any other dynamic languages ... the redirect is going to get in the way, and you won't be able to use PHP in the search results.

You can switch how Article Manager handles dynamic parsing by going to Admin > General Settings > Dynamic SSI and Code Parsing.

I hope this helps. :)

Donna

--
support@interactivetools.com