Content-Security-Policy settings are not respected in new version of Jupyter Hub.
Following screen capture is demonstrating how same settings worked in JupyterHub v1.4.0 and in v1.5.1 it doesn’t work any more:
In order to debug the problem I tried to dive into logs according to:
…no sign of any error in any file
Same settings on both JupyterHub instances
JupyterHub settings in file /opt/tljh/config/jupyterhub_config.d/jupyterhub_config.py:
Well, that seems like Chrome is blocking cross origin request. I could make it work on Firefox 114 on my kubuntu workstation. As JupyterHub 1.5.1 is bit too old, I had to downgrade SQLAlchemy<2. I used exactly your config and env (py 3.9 and hub 1.5.1) and it worked!
@mahendrapaipuri you’re right, it works on Firefox, my mistake! Thank you so much for taking the time replicating my env.
It looks like the origin of the problem is chromium browsers core. I wonder if there’s something I can do to make it work for chromium based browsers (Chrome, Brave, Vivaldi, etc.). Any “dive-in” direction would be highly appreciated.
I’m using TLJH installation.
BTW, I simplified the setup with only one file now: /opt/tljh/config/jupyterhub_config.d/jupyterhub_config.py: