-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error 403 with ein over proxy #76
Comments
This isn't really possible for me to debug, AFAICT. The websocket library offers a way to send headers. Those headers can be authentication headers. Websockets aren't going to cause authentication problems itself - that's the server's doing. It could be that the necessary info isn't coming over via websockets to the server. I can think of a few reasons for this.
Can you look at the above possibilities and let me know? |
1
|
2
|
Thanks for the response. What is interesting is that you have cookies for this site already in emacs. Do you know where those come from? Can you connect to the notebook in emacs with eww? If this is an internal server for your organization, is there any chance you can ask what authentication they are expecting? Or if they have logs of when you access with websockets, to see what the problem is on the server side. There's a few things here that could be interesting - what you can try to do is to add some of these headers to the |
Thank you!
Yes, they are written by Emacs/curl. |
Sort of... |
this is the standard jupyter server:
with token authentication
here is the relevant part of the jupyter server log:
|
trace:
same error
|
Interesting, thanks for sharing. Let's summarize - and let me know if anything I say is wrong.
My guess is that it has to be a proxy issue - that seems to be the only difference from normal. Is there any relevant info on the proxy you are using you can share? I don't know much about proxies, but I do know that websocket doesn't have any special support for them. Also, have you seen jupyter/notebook#3389? It seems very similar to your issue. |
could be - my jupyter works with chrome & firefox but not with |
There is a glimpse of hope - when I append |
Same error on ubuntu 18.04 jupyter 6.1.6 ` ` |
@sam-s Interesting that the token works. I wonder if this means that ein should be setting it. The websocket library is agnostic about such things. It seems like, from the headers you have provided, that ein is asking for it but not passing it along to the websocket library. Does that sound plausible to you? @cw1427 Can you also try to manually append the token in the same way described above to see if that solves your problem? Is there anything unusual about your jupyter installation? |
according to @dickmao in tkf/emacs-request#193 (comment),
the bug described in tkf/emacs-request#193 and millejoh/emacs-ipython-notebook#754 is coming from
websocket
.Please let me know if I could be of any assistance in debugging.
thank you.
The text was updated successfully, but these errors were encountered: