×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
We currently run two web sites on our iSeries. One for students and one for employees. Both use the same url domain
https://as400sec.pct.edu/SISaccess/ for students and
https://as400sec.pct.edu/webapps/eswlogin.pgm/ for employees. We currently have some redirects setup on an IIS server so a user can use www.pct.edu/sis<
http://www.pct.edu/sis> or www.pct.edu/eis<
http://www.pct.edu/eis> to get to the correct page to logon. We would like to use sis.pct.edu and eis.pct.edu and send the initial connection to one the two logon pages. I have been reading up on url rewriting which led me to redirects and RedirectPermanent and 301 messages and even domain aliases. Anyone have any experience in doing this and have any thoughts as to which is the best option for what we want to do? Ultimately I think we would want to use sis.pct.edu and eis.pct.edu as the domain in all the links in the two different applications but that would get into using multiple Verisign certificates and changing all our current links
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.