You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
URLs using http instead of https will be blocked by the browser due to a mixed content error. Statuses set up using an http URL will fail - currently, the UI will show a generic error that doesn't explain the source of the problem (it is only available by looking at the browser console).
Desired Behaviour
At a minimum, check for URLs using HTTP only, and block those URLs from being set up as a service.
When an HTTP URL is detected, the user should be presented with an informative message in the Add Service modal indicating the cause of the problem.
The user should be advised to test the URL with HTTPS - if it works, they can use the HTTPS URL; if it doesn't work, the URL can't be used in Status Pages.
The text was updated successfully, but these errors were encountered:
added TextFieldWrapper component to status-page.js so that I can use validationText property when a service is being edited
in main-page.js check the url for the service logo to ensure it uses secure url
3 hrs
Summary
URLs using http instead of https will be blocked by the browser due to a mixed content error. Statuses set up using an http URL will fail - currently, the UI will show a generic error that doesn't explain the source of the problem (it is only available by looking at the browser console).
Desired Behaviour
At a minimum, check for URLs using HTTP only, and block those URLs from being set up as a service.
When an HTTP URL is detected, the user should be presented with an informative message in the Add Service modal indicating the cause of the problem.
The user should be advised to test the URL with HTTPS - if it works, they can use the HTTPS URL; if it doesn't work, the URL can't be used in Status Pages.
The text was updated successfully, but these errors were encountered: