Closed jvhaarst closed 10 years ago
URL for assets aren't exactly hardcoded. They are generated by a helper method - uri
- as you would have noticed.
For relative urls to work in a sub-uri deployment, it is essential that the uri ends in a trailing slash. That is, antgenomes.org/blast/
will work, but for antgenomes.org/blast
browser will try to load assets from the base uri antgenomes.org/
. To work around that you would either rewrite urls (mod_rewrite) or make assets available on the base url. Using the uri
helper felt like the simplest solution back then.
This is what I did for reverse proxy setup on http://antgenomes.org/blast - https://github.com/yeban/sequenceserver/commit/aa0d1ab98f62cb51f2ca8c431b4695b3919280ed
I think I will change to relative URLs now. Thanks for bringing this up!
That's great !
via e924f47d1879f7a3e9086d32a5f1d36ca014266d.
A release could take some time though.
I have just been bitten by the fact that sequenceserver encodes the URLs for the css and js directories with hard paths. Somehow this messed up the proxying by Apache, after I made the paths relative (and thus removing most of the templating), it now works. The resulting head looks like this:
Is there a reason why you do not make the URLs to the css and js directories relative links ?