https://www.infopathdev.com:443/forums/41.aspxIf you're not sure where to ask your question, ask it here. If necessary, our moderators will make sure it gets classified in the correct board.enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/6490.aspxSun, 30 Jan 2005 05:37:24 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:6490Patrick Halstead0https://www.infopathdev.com:443/forums/thread/6490.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=6490Interesting scenario and one that I have not heard of before. :) I wonder if you can't make it https on both internal and external? Another idea, would be to make the solution URN-based. Use the Regform tool. Then, the XML files won't have a URL in the name. The downside is that users will have to install the form, and auto-update won't work.https://www.infopathdev.com:443/forums/thread/4545.aspxWed, 26 Jan 2005 18:38:34 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:4545pxm40https://www.infopathdev.com:443/forums/thread/4545.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=4545I am publishing forms to an web site that is available on our intranet as an HTTP server, but is available to external users as an HTTPS server.<br /><br />I am having a problem when InfoPath tries to load the template specified in the processing instruction of an XML document. If the form is loaded from our intranet site, everything is fine since the template is stamped with<a target="_blank" href=HTTP://.....>HTTP://.....</a><br /><br />However, external users are forced to access the site via HTTPS and then they get the "template has been moved" message and are unable to open the template.<br /><br />If I save the template from outside our intranet (using HTTPS), then internal uses cannot open the template unless they remember to switch to HTTPS before they try and open the XML document. This is not very appealing to me since there are only a few users who are external, but a large number who are internal.<br /><br />Anyone have any suggestions on how to correct this? Is there a way to modify the PI at the desktop of the external users to change the HTTP in the XML to HTTPS? Or, is there a way to bypass this check? <br /><br />Pat