Open ComLock opened 8 years ago
Hi @ComLock!
Sorry for the late reply - for some reason I haven't seen these issues before now.
Sounds like a good idea, I'll look into this sometime this week if it's still a usecase.
As I see it, there are no drawbacks of using absolute paths as default, right?
Actually, for me the application was unusable. We use a reverse proxy from domain.no:80/443 to loclhost:8080. When returning absolute URL's, the favicon wil not work as the url it implements in the HTML is http://localhost:8080/.....
I'm sorry to hear that @theberzer . Feel free to submit a pull request, and I'll look at it right away.
It would be nice to have the option of getting absolute rather than relative paths when using the favicon app. For instance when a site is providing a decorator with menus, footers etc to be used on another domain...