Harmonizome and Enrichr behavior in static html notebook widget

[cornhundred]

Getting errors like this for Enrichr and Harmonizome in static html files with widgets

Failed to load https://amp.pharm.mssm.edu/Harmonizome/api/1.0/gene/MT: The 'Access-Control-Allow-Origin' header has a value 'null' that is not equal to the supplied origin. Origin 'null' is therefore not allowed access.

Failed to load https://amp.pharm.mssm.edu/Enrichr/addList: The 'Access-Control-Allow-Origin' header has a value 'null' that is not equal to the supplied origin. Origin 'null' is therefore not allowed access.

[sherry-jenkins]

Will look into it.

Sherry Jenkins, MS Program Manager II Mount Sinai Center for Bioinformatics (MSCB) BD2K-LINCS Data Coordination and Integration Center (DCIC) Department of Pharmacological Sciences Icahn School of Medicine at Mount Sinai One Gustave L. Levy Place, Box 1603 New York, NY 10029-6574 212-241-7265

Follow us on Twitter @MaayanLabhttps://twitter.com/MaayanLab @BD2KLINCSDCIChttps://twitter.com/BD2KLINCSDCIC http://labs.icahn.mssm.edu/maayanlab/ http://icahn.mssm.edu/research/bioinformatics http://lincs-dcic.orghttp://lincs-dcic.org/

From: Nicolas Fernandez [mailto:[email protected]] Sent: Tuesday, April 10, 2018 12:52 PM To: MaayanLab/clustergrammer-widget Cc: Subscribed Subject: [MaayanLab/clustergrammer-widget] Harmonizome and Enrichr behavior in static html notebook widget (#6)

Getting errors like this for Enrichr and Harmonizome in static html files with widgets

Failed to load https://amp.pharm.mssm.edu/Harmonizome/api/1.0/gene/MT: The 'Access-Control-Allow-Origin' header has a value 'null' that is not equal to the supplied origin. Origin 'null' is therefore not allowed access.

Failed to load https://amp.pharm.mssm.edu/Enrichr/addList: The 'Access-Control-Allow-Origin' header has a value 'null' that is not equal to the supplied origin. Origin 'null' is therefore not allowed access.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_MaayanLab_clustergrammer-2Dwidget_issues_6&d=DwMCaQ&c=shNJtf5dKgNcPZ6Yh64b-A&r=DRhuvi1TiuE1B6MsdHBUy3jdJ-3z1n20Dnb96voIQDk&m=nyTy4gXxKSx6ksx5y3gjbd2eXXGfc7A0cjfb6eA5atc&s=RnV2x3GVWDcBaC1SxhDlSqcKVoyU3GCkAtqXOgfXA0k&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ALZTFpq2-2D5Pg68Dc4PMS7naelEW9WNecks5tnONAgaJpZM4TOofA&d=DwMCaQ&c=shNJtf5dKgNcPZ6Yh64b-A&r=DRhuvi1TiuE1B6MsdHBUy3jdJ-3z1n20Dnb96voIQDk&m=nyTy4gXxKSx6ksx5y3gjbd2eXXGfc7A0cjfb6eA5atc&s=AL7B-PuDgZJkuXyDbanGz15QI_FXTTL-_WcR6moviq0&e=.

[cornhundred]

Hi Sherry,

It seems to be a new problem I'm getting. I'll be looking into it also and keep you all updated.

Best, Nick

[u8sand]

@cornhundred CORS still seems to be enabled--one way to test it is with this link

Noting the CORSFilter code, if the Origin is null it suggests the request isn't cross-origin; Harmonizome's CORSFilter sends back specific allow origin responses requiring that Origin is specified in the request header. We could potentially just send back Allow-Origin: * but this may be a browser-specific setting. I don't seem to be experiencing it locally.

Could you potentially capture the network request header of the packets causing this and share?

[cornhundred]

Thanks @u8sand, I will look into this. I also added a link to a Jupyter notebook HTML file where the error can be reproduced. If you download the html file, open it in a browser, open dev tools and view the console, and then mouseover gene/row names to make get requests to the Harmonizome then you should see the same error.

[u8sand]

@cornhundred So I tested that file locally on Chrome, Safari, and Firefox on two different computers and all of them seem to work so I'm not entirely sure what's different about your environment.

[cornhundred]

Thanks @u8sand, that's good it is working on your end. I'll have to do more troubleshooting and will report back with what I find.

[cornhundred]

It's working on Firefox, but not chrome. Maybe an update to Chrome broke something?