Closed minrk closed 7 months ago
Thanks @minrk
I suspect the tests are failing because we need to now also specify the XSRF token in https://github.com/jupyterhub/nbgitpuller/blob/518c9c8af7f51c7c9797d1063c9ab89766fb9e52/tests/test_api.py#L16. But given that's coming from a python client, I'd have thought that it shouldn't have issues as long as the token is present?
Correct, if a token is present, xsrf shouldn't be checked. I'll have a look
403 was because I had an unrelated change in here to turn 302 into 403 while I was testing (302 to login on the EventSource isn't going to work). I've pulled that out and will do a separate PR.
Failure was unrelated, pulled out to #347
JupyterHub 4.1 increases strictness of xsrf checks (omitting it is no longer allowed on GET requests that are
Sec-Fetch: cors
, which includes this EventStream).closes #344