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

Check dashboard server side #159

Merged
merged 6 commits into from
Dec 15, 2020

Conversation

ian-r-rose
Copy link
Collaborator

This should resolve a number of long-running issues around user-provided dashboard URLs (that is to say, ones that are entered into the URL box, not those managed by the cluster manager). Previously we did a couple of things client-side:

  1. Check to see if the url is valid
  2. Load the list of individual plots from the bokeh server

This is for primarily historical reasons, as the server-side component of this extension did not always exist. It wound up causing a number of issues around CORS and mixed content. This moves the above checks to a new tornado handler on the server side, which have fewer such restrictions. It also allows us to more easily follow redirects.

Note: this still embeds the iframes directly from the bokeh server. We may want to also proxy those under the notebook server (as is done with the clusters launched by the labextension itself), but that can be in a follow-up, I think.

Fixes #158, fixes #137, probably fixes #32

Ian Rose added 5 commits December 9, 2020 11:20
side. This allows us to avoid CORS or mixed content errors when
determining whether a user-provided dashboard is valid.
that is captured in `effectiveUrl`, which is used to construct dashboard
chart urls.
Close nonexistent panes, rename ones that have a different label.
@mrocklin
Copy link
Member

mrocklin commented Dec 9, 2020 via email

@ian-r-rose
Copy link
Collaborator Author

Unless there are objections, I'll merge this today

@jrbourbeau
Copy link
Member

FWIW I just tested out the changes here using a Coiled cluster and everything worked as expected (i.e. we followed the redirect mentioned in #158)

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

Successfully merging this pull request may close these issues.

Follow redirect in search box List of routes no longer being detected? 500 GET: missing dask-logo.svg
3 participants