All geek questions in one place

HTML5 Cache Manifest works on top of http, but not https

My google-fu doesn't seem sniffing today, so here it is ...

I have a django application sitting on top of apache using wsgi. I am trying to make this work offline. I am serving a cache manifest file from a django url with the correct mimetype type and a header without a cache. I have a link in a template that looks like

<html lang="en" manifest="/myPath/manifest/">

To debug this problem, I first use the simplest manifest file

CACHE MANIFEST

NETWORK:

*

However, this gives me the following errors in chrome when I try to execute it through the https interface.

Application cache creation using manifest https://127.0.0.1/myPath/manifest/ Application cache validation event Application cache error event: Manifest error (-1) https://127.0.0.1/myPath/manifest/

When serving via http, it works correctly. I use my own security certificate on my development machine. This is the only thing I can think of that can make the difference between http and https serving the same manifest file (using relative links so that the origin is correct). What causes the difference between http and https and how do I fix it?

+4
source share
1 answer

I would blame your self-signed certificate.

Chrome and Firefox, if scary-looking warning dialogs weren’t enough, pretty self-signed certificate anal. For example, HSTS does not work with self-signed certificates in any browser.

+7
source

Source: https://habr.com/ru/post/1348014/

More articles:


All Articles