Closed albertoriva closed 3 months ago
Hi @albertoriva It's temporary, we are having some issues with the database server who provides mysql support for the legacy browser, working on it, should be back online next 1-2 weeks, sorry for the inconvenience.
Hi @albertoriva sorry for the inconvenience again, the legacy browser should be back now. Let me know if there is any issue. (there are indeed failed drives on that server, we are going to replace them, so there maybe some short time in the near future)
Hello Daofeng,
Thank you for your note, glad to hear that the browser is back.
By the way, I would really like to be able to switch to the new browser, but I still can't get it to understand https URLs in track hubs. Any updates on that issue?
Thank you!
Alberto
On Tue, Apr 16, 2024 at 5:35 PM Daofeng Li @.***> wrote:
Hi @albertoriva https://github.com/albertoriva sorry for the inconvenience again, the legacy browser should be back now. Let me know if there is any issue. (there are indeed failed drives on that server, we are going to replace them, so there maybe some short time in the near future)
— Reply to this email directly, view it on GitHub https://github.com/lidaof/eg-react/issues/348#issuecomment-2059959853, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTWE6R4JEZ56BJPVLCDYRLY5WKSLAVCNFSM6AAAAABGFV73BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJZHE2TSOBVGM . You are receiving this because you were mentioned.Message ID: @.***>
Hi @albertoriva , our pleasure.
Both browsers can be accessed with http or https URL, we know some lab doesn't have https enabled web server, so if your data is hosted with http protocol, you can use the http version of the browser.
Sorry I wasn't clear. I was referring to loading a remote data hub using a JSON file. This is what happens when I try:
[image: image.png]
The same hub works perfectly in the legacy browser. Here's the address:
https://lichtlab.cancer.ufl.edu/reports/MDS//NS3526-noIgG/NS3526/hub.json
Thank you!
On Wed, Apr 17, 2024 at 10:29 AM Daofeng Li @.***> wrote:
Hi @albertoriva https://github.com/albertoriva , our pleasure.
Both browsers can be accessed with http or https URL, we know some lab doesn't have https enabled web server, so if your data is hosted with http protocol, you can use the http version of the browser.
— Reply to this email directly, view it on GitHub https://github.com/lidaof/eg-react/issues/348#issuecomment-2061398774, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTWE6WI5TJG373MSJFGDETY52BMFAVCNFSM6AAAAABGFV73BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRRGM4TQNZXGQ . You are receiving this because you were mentioned.Message ID: @.***>
HI @albertoriva i see, yes, so far I haven't found a good JS library can parse password protected URL files..will keep exploring...thanks!
Daofeng,
But this URL is not password protected...
Alberto
On Thu, Apr 18, 2024 at 10:37 AM Daofeng Li @.***> wrote:
HI @albertoriva https://github.com/albertoriva i see, yes, so far I haven't found a good JS library can parse password protected URL files..will keep exploring...thanks!
— Reply to this email directly, view it on GitHub https://github.com/lidaof/eg-react/issues/348#issuecomment-2064040105, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTWE6QIXZH2YT3Y7ZHJXDDY57LELAVCNFSM6AAAAABGFV73BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRUGA2DAMJQGU . You are receiving this because you were mentioned.Message ID: @.***>
Hi @albertoriva i mean the URLs in your json file, for each track file
Right, sorry for the confusion. I remove the passwords from the URLs, and it still gives the same error (while it loads perfectly in the legacy browser).
Thank you!
On Thu, Apr 18, 2024 at 11:17 AM Daofeng Li @.***> wrote:
Hi @albertoriva https://github.com/albertoriva i mean the URLs in your json file, for each track file
— Reply to this email directly, view it on GitHub https://github.com/lidaof/eg-react/issues/348#issuecomment-2064192527, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTWE6UW46DQMN7VSTRZMXTY57PYJAVCNFSM6AAAAABGFV73BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRUGE4TENJSG4 . You are receiving this because you were mentioned.Message ID: @.***>
Ha, i see, yes, i see the problem is you need to enable CORS on your webserver. The new browser users entirely JavaScript, the legacy browser uses a C backend which fetches data doesn't need CORS..sorry for the inconvenience....It's the JS default security setup. https://eg.readthedocs.io/en/latest/tracks.html#configure-your-webserver-to-enable-cors
Yes, it works now! Thank you!!
Alberto
On Thu, Apr 18, 2024 at 5:15 PM Daofeng Li @.***> wrote:
Ha, i see, yes, i see the problem is you need to enable CORS on your webserver. The new browser users entirely JavaScript, the legacy browser uses a C backend which fetches data doesn't need CORS..sorry for the inconvenience....It's the JS default security setup.
https://eg.readthedocs.io/en/latest/tracks.html#configure-your-webserver-to-enable-cors
— Reply to this email directly, view it on GitHub https://github.com/lidaof/eg-react/issues/348#issuecomment-2065335887, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTWE6QOSYTKIDXYP626J4LY6AZVJAVCNFSM6AAAAABGFV73BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRVGMZTKOBYG4 . You are receiving this because you were mentioned.Message ID: @.***>
Hello,
I am getting a 404 error when trying to access the legacy browser:
"The requested URL /legacy/ was not found on this server."
Is this temporary, or is the old browser gone?