 |
Need a knowledge base like this for your business?
HTTPS Support
 | By Kim Dixon, MyPhotoApp Training Guru Created: November 5, 2017, 4:59 pm UTC Last updated: May 18, 2021, 11:13 pm UTC |
MyPhotoApp continues to support both HTTPS and HTTP URL addresses. However, it is possible that in the future support for HTTP may cease.
Logging on to the MyPhotoApp Builder
Logging on to the MyPhotoApp Builder
When you log in to the builder, you can choose to use either use:
- https://builder.mp-app.com
- http://builder.mp-app.com or
When you log into the builder the URL you choose determines whether your apps will use an HTTPS or HTTP URL when they are published. It is best to choose to work in one version of the Builder and we recommend that everyone should now be working in the secure HTTPS builder.
What happens when I change from using HTTP to HTTPS to log in to the Builder?
If you have previously been logging in to the builder using http://builder.mp-app.com all existing Apps will have HTTP in their URL like this:
http://m.mp-app.com/kim/DigitalBusinessCard
When you switch to logging in to the builder using https://builder.mp-app.com the following applies:
When you switch to logging in to the builder using https://builder.mp-app.com the following applies:
- Existing Apps with HTTP will continue to work without the need to republish them.
- To access existing apps with HTTP using the HTTPS URL you will need to republish the App.
- Apps published in the HTTPS builder will work with either URL
- Apps installed by clients using HTTP will continue to work whether republished or not.
- Apps created using a Custom URL prior to May 15 2021 that have not been updated to the new SSL settings will continue to use HTTP by default.
- Apps created using a Custom URL after May 15 2021 using the new settings will use HTTPS by default
IMPORTANT: When logged into the builder using HTTPS the publish status window will display ALL App URLs as HTTPS even if they were previously published as HTTP. Trying to access an App published as HTTP using the HTTPS URL will result in missing image errors. To resolve this simply republish the App to use HTTPS before sharing. Apps created in Brands with a Custom URL that has not been updated to the new HTTPS settings will still be displayed as HTTP and only work with that URL.
To update your Custome URL to take advantage of the SSL support you will need to change your domain or subdomain setting to the new ones and re-verify the Custom URL. You can find out more about how to update an existing Custom URL in this article:
How To Update Your Existing HTTP Custom URL to HTTPS
HTTPS For New Custom URL's
How To Update Your Existing HTTP Custom URL to HTTPS
HTTPS For New Custom URL's
MyPhotApp now includes SSL support for Custom URLs with your subscription. When you add a custom URL to a Brand via the SETUP TAB and Custom URL option the builder will now automatically apply HTTPS to Apps created in that Brand providing you are logged in to the HTTPS version of the builder.
Browser Warnings
Recent changes to how Google and Apple IOS deals with HTTP sites have led to App users receiving browser messages warning that HTTP URLs may pose a threat. This type of warning is only actually a concern IF personal financial details are input into a site using HTTP rather than the more secure HTTPS. Any links to third party payment options added to your Apps are NOT processed by MyPhotoApp but by the third-party provider and therefore remain secure.
To avoid these warning we recommend that you switch to working in the HTTPS version of the builder.
If you continue to use HTTP builder you can do so without any risk to your clients BUT you should consider educating your clients that such warnings are only there for their safety and are only relevant when dealing with financial transaction carried out on the site they visit and can therefore be safely ignored when accessing their photo apps even if it has a shopping cart in it.
To avoid these warning we recommend that you switch to working in the HTTPS version of the builder.
If you continue to use HTTP builder you can do so without any risk to your clients BUT you should consider educating your clients that such warnings are only there for their safety and are only relevant when dealing with financial transaction carried out on the site they visit and can therefore be safely ignored when accessing their photo apps even if it has a shopping cart in it.