• This is only a problem with the Chrome browser, not Edge.

    These are 4 snapshots taken by a remote camera that should display. These url’s are html code on a WordPress page that is an “http” address, not “https”. The site has a valid SSL certificate. The site has the WP Force SSL plugin but deactivating it doesn’t change behavior. When inspecting the element in Chrome, I see no that the url continues to be “https” when the actual address of the camera is “http”.

    QUESTION: How can I prevent the url being changed form http to https?

    Thank you in advance
    Mike

    UPDATE: Changing the protocol in the Chrome inspection pane doesn’t allow the image to load within WordPress. However, with the “http” protocol I am able to “open in new window”.

    • This topic was modified 4 years, 4 months ago by Steven Stern (sterndata).
    • This topic was modified 4 years, 4 months ago by Mike8857. Reason: Additional information

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Could you please point the exact area on the site where you are seeing the issue?

    I just tested your site and seems to be running as HTTPS.

    Just a thought – have you tried reaching out to your hosting provider? they might be able to help you.

    Thread Starter Mike8857

    (@mike8857)

    @a2hostinglk – Thank you for responding. The url points to a password protected area of the web site. I posted a test user earlier but subsequently learned that this is a violation of the forum. This makes sense.

    I am unsure as to where to start. As I said, the html for the cameras are “http” but when inspecting the element in Chrome, I see that the url has been converted to “https”. As you suggest, I’ll contact the service provider.

    Thank you

    Thread Starter Mike8857

    (@mike8857)

    I checked with my ISP. They are able to prevent HTTPS for the whole site not for individual urls.

    Again the page contains HTTP image but when opened in Chrome, there is no image. Edge, Firefox and Safari are fine. What is it about Chrome?

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Some url’s should not be converted from http to https’ is closed to new replies.