issue with SSL redirect

Posted By pfkoss Mon 2 Nov 2015
Add to Favorites1
Author Message
pfkoss
 Posted Mon 2 Nov 2015
Supreme Being

Supreme Being - (3,809 reputation)Supreme Being - (3,809 reputation)Supreme Being - (3,809 reputation)Supreme Being - (3,809 reputation)Supreme Being - (3,809 reputation)Supreme Being - (3,809 reputation)Supreme Being - (3,809 reputation)Supreme Being - (3,809 reputation)Supreme Being - (3,809 reputation)

Group: Forum Members
Last Active: Fri 19 Jan 2018
Posts: 7, Visits: 14
Just enabled SSL on a site.

Set up is as follows

IIS7 running many different websites

Kartris site setup
HTTP bound to port 8130
HTTPS bound to port 8131

external IP address is redirected through firewall to internal IP as follows (obviously not real IPs)

111.111.111.111:80 traffic redirected to 222.222.222.222:8130
111.111.111.111:443 traffic redirected to 222.222.222.222:8131



If I navigate http:\\site.domain.com everything is fine.

if I navigate https:\\site.domain.com the site hangs and then redirects to site.domain.com:8131/default.aspx

I'm assuming there is a redirect somewhere in the code that is catching the SSL traffic and forcing the redirect but I can't seem to find it and I don't know why it is adding the port number.

I've tried this with the SSL config flag on and off and there is no difference.

Anyone have any ideas ?
Paul
 Posted Tue 3 Nov 2015
große Käse

große Käse - (449,864 reputation)große Käse - (449,864 reputation)große Käse - (449,864 reputation)große Käse - (449,864 reputation)große Käse - (449,864 reputation)große Käse - (449,864 reputation)große Käse - (449,864 reputation)große Käse - (449,864 reputation)große Käse - (449,864 reputation)

Group: Administrators
Last Active: Fri 15 Sep 2023
Posts: 806, Visits: 2,737
There is a code for handling SSL in app_code/security.vb

Kartris is designed to switch to SSL on pages that require it by redirecting to https from http. I don't think the port info is being added by kartris in this redirect, though to confirm this you could set the app pool to classic rather than integrated, and then test on a static file like the favicon.ico (in classic pool, this won't fire up any of the Kartris code, in integrated it will). If that gets redirected, then it's come from IIS and not kartris.

If it's coming from kartris then would need to tinker with the SSL functions i think to fix this.


--
If my post solves your issue, can you 'Mark as Answer' so it's easier for other users to find in future.

If you would like to be informed of new features, new releases, developments and occasional special bonuses, please sign up to our mailing list: http://bit.ly/19sKMZb
pfkoss Marked As Answer
 Posted Mon 9 Nov 2015
Supreme Being

Supreme Being - (3,809 reputation)Supreme Being - (3,809 reputation)Supreme Being - (3,809 reputation)Supreme Being - (3,809 reputation)Supreme Being - (3,809 reputation)Supreme Being - (3,809 reputation)Supreme Being - (3,809 reputation)Supreme Being - (3,809 reputation)Supreme Being - (3,809 reputation)

Group: Forum Members
Last Active: Fri 19 Jan 2018
Posts: 7, Visits: 14
Turns out the issue was basic. We are using port binding in IIS for the multiple site we run. (only one of which is kartris). Kartriss / Authorize.net will only allow for standard ports and will not work with non-standard ports. You must have site running on 80/443

Similar Topics

Expand / Collapse

Reading This Topic

Expand / Collapse

Back To Top