-
Notifications
You must be signed in to change notification settings - Fork 8
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
Dealing with access-protected files behind cookies/https Web server #6
Comments
Jose, there is an issue with earlier versions of the JSAMP hub not being Can you try it with a more recent version of the JSAMP hub Mark On Fri, 4 Jul 2014, Jose Enrique Ruiz wrote:
Mark Taylor Astronomical Programmer Physics, Bristol University, UK |
Hi Mark Hope it helps ! |
OK, it was worth a go. The way that samp.js communicates with the hub from within the browser can get rather complicated, and I don't have time right now to look at it very closely. It may be that it's effectively impossible to get it working because of the security architecture. Or it may not. If you want to investigate further, you could try turning on HTTP-level logging of the web profile communications; to do this start the hub with |
Ok, thanks for the quick reply. |
Hi SAMPers
I have sucessfully installed SAMP Web Profile in a https-protected IPython Notebook Server with sampjs. See https://www.youtube.com/watch?v=Q3v1vFZyIAQ
It works really well with non-protected files, but I guess SAMP-enabled desktop apps cannot access files produced inside a https-protected IPython Notebook Server. Is there any existing (rapid) solution to deal with access-protected files?
The text was updated successfully, but these errors were encountered: