-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Issue Creating New Notebooks in IE only #2594
Milestone
Comments
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have an application that is framing user servers spawned by SystemUserSpawner. The notebook servers are configured to use no-tab mode in order to keep everything within the frame.
The issue arises when a user wants to create a new notebook. Upon selecting which kernel to use for their new notebook, the user is presented with a 404 page. This only occurs if the user is using Internet Explorer. Chrome and Firefox work perfectly, as does Microsoft Edge on Win10.
The logs and network traffic indicate that there is a GET request being fired on /user//undefined. This request obviously returns a 404 because undefined doesn't exist. After this call the normal, expected POST request to create the notebook is fired, and returns successfully; however, the 404 page doesn't re-route to the new URL. The network logs are as follows:
The relevant notebook server logs are:
In both of these examples we can see the GET firing before creation. The odd thing to me is the fact that this initial GET request is never called in Chrome or Firefox.
I've also ran IE tests outside of the frame in default tabbed mode and I get the same results. The new tab that is created displays the 404 page; however, sometimes the 404 page will re-route itself to the correct URL after the notebook is created.
I've dug around in the source code to attempt to find what might be causing this rogue GET request, but I was unable to pinpoint it.
Any help on this subject would be greatly appreciated. Thanks.
The text was updated successfully, but these errors were encountered: