Open jmhobbs opened 10 years ago
I can tackle this, but there are two ways (maybe more) to go about it:
I think option 1 is easier to implement and keeps the logic in one place, but we'd probably have to rely on a regex there until Chrome 32 comes out with its built-in URL goodies. I also am not sure how this affects file paths as I don't really use them much, but I assume if we just check for "[http|https|file]:" we should be fine.
Thoughts on which approach you'd prefer?
I would go with #1. If you look at feature/path-remapping you can see where I'm already normalizing a base path, so we may as well add protocol there too.
Hi, is this going to be implemented? I'm interested in this feature too.
Hi @ShacharHarshuv! This project has long laid dormant, so I don't know when or if it would happen. Happy to accept PR's though!
Notably, https vs. http.