![]() ![]() ![]() Non-secure content can theoretically be read or modified by attackers, even though the parent page is served over HTTPs, so is normal and recommended that the browser warns the user. The browser blocks your XHR connections because they are HTTP connections initiated from a HTTPS page (mixed-content warning). The connection are done using the name (not the IP) of the device which is resolved to the private IPĭoes a http header exists that allows insecure connections to a specific URL ? (like CORS for cross domain) Plex solves the problem with a Dynamic DNS and a wildcard certificate. You can issue a self-signed certificate to a private address, but a trusted CA will not issue a certificate to a private address because it can not verify its identity.įor example a certificate issued to 192.168.0.1 would be theoretically valid in any context, and this should not be allowed by a trusted CA Is it possible to obtain a certificate for a private IP address ?Ī certificate can be bound to an IP address (see this).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |