Open anderspitman opened 4 years ago
Thank you @anderspitman related to the old backend expiration issues @yiq mentioned at lab meeting, correct?
This particular request ws://null/
can be another reason why gene.iobio is shown as not secure??
Console message:
The other reason that you have mentioned is http://iobio for image source. Related to issue: #471
@mvelinder it's not completely related. I would say that is a higher priority so we can turn off the old backend. This is essentially cleanup.
Is this pressing?
I would say no (but it needs to be kept open), unless it's causing https://github.com/iobio/gene.iobio.vue/issues/755, then yes.
The amount of code that needs to be removed to fix the particular error @adityaekawade mentions should be quite easy to take care of.
Removing iobio.js, iobio.min.js, and binary.js from here:
https://github.com/iobio/gene.iobio.vue/tree/master/client/app/third-party
and here:
https://github.com/iobio/gene.iobio.vue/blob/master/server/views/index.html
may be it.
But there are a bunch of other unused files in there that we need to clean up at some point.
@anderspitman @tonydisera Do we still need to address this?
Yep
Yep.
I noticed that gene is still making requests to
ws://null/
. This is an artifact of the old backend API which used websockets. We need to remove that code, as well as a bunch of other things involved in the old local file support (bgzf, compression, etc).