Skip to content
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

Notebook Server replies to Plot3d-Data-Request with Status 301 #9268

Closed
sagetrac-ManDay mannequin opened this issue Jun 18, 2010 · 3 comments
Closed

Notebook Server replies to Plot3d-Data-Request with Status 301 #9268

sagetrac-ManDay mannequin opened this issue Jun 18, 2010 · 3 comments

Comments

@sagetrac-ManDay
Copy link
Mannequin

sagetrac-ManDay mannequin commented Jun 18, 2010

This issue has long caused problems, although many people managed to get it fixed without actually knowing what caused it. As discussed in all detail in the following thread

http://groups.google.com/group/sage-notebook/browse_thread/thread/9191e031224a3ce9

JMol requests the data for the plot3d from the Sage backend. When it does so, on some occasions it receives a 301 Moved Permanently which Java is not following but interprets as 200 and parses the content - which then causes the error.

This is partly a client-side Java problem as Java should perhaps follow the 301 to the new location and then pass the data transparently but also Sage shouldn't provide a 301'd location in the first place.

Further details, such as the fact that this does not happen for applets which are part of a published worksheet can be found in the thread.

Can be fixed by making JMol pointing to the correct location or make Sage transparently return the data instead of a 301.

This problem occurs with both, the open IcedTea (OpenJDK) and propritary Sun Java in Firefox 3.6 on Ubuntu 10.4LTS.

On a sidenote, I assume that other people do not have this problem because they might have additional packages installed which compensate for the 301.

CC: @kcrisman @jhpalmieri

Component: notebook

Keywords: notebook java jmol black

Issue created by migration from https://trac.sagemath.org/ticket/9268

@fchapoton
Copy link
Contributor

comment:1

ancient ticket about deprecated sagenb, can we close ?

@kcrisman
Copy link
Member

comment:2

There were a number of wonky things like this we never saw often enough to diagnose, true.

@fchapoton
Copy link
Contributor

comment:3

thx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants