ISM Knowledgebase | Back To ISM Site
Search:     Advanced search

Sage Hosting MASISAPI.ini configuration

Article ID: 22
Last updated: 19 Oct, 2009
Add comment
Views: 494
Comments: 0
Posted: 19 Oct, 2009
by: Goldsmith A.
Updated: 19 Oct, 2009
by: Goldsmith A.

October 30, 2007

 

Sage hosting remaps port 443 (external SSL) to 442 (internally).  So the MASISAPI.INI file has to be configured differently.  A picture's worth a thousand words, so here’s how a Sage hosting MASISAPI.INI file looks (this is the actual working file for LabLink Scientific Supply, Inc.):

 

[debugging]

 

[HTTP Remappings]
host206.ebm.bestsoftwarehost.com=http://65.81.72.108:2953
host206.ebm.bestsoftwarehost.com:442=http://65.81.72.108:2953

 

[HTTPS Remappings]

 

[Http Proxy Remappings]
host206.ebm.bestsoftwarehost.com:442=https://host206.ebm.bestsoftwarehost.com

 

Note the last line.  This apparently lets the ProvideX web engine inject the appropriate base href tag (which, in turn, allows the calling browser to fetch CSS and JavaScript files properly).  Note also that the [HTTPS Remappings] section is empty...but that makes sense if SSL requests are being remapped by the firewall to port 442 (which isn't standard SSL).  Hence the second line in the [HTTP Remappings] section.

This article was:   Helpful | Not Helpful Add comment
Also listed in
folder MAS 90
folder MAS 200

Prev   Next
How to rename the 3 Buttons at the Bottom of B2B Checkout in...     Sage EBusiness Manager SEO White Paper

RSS