Updates to handle linked relative resources when using CDNJS local cache option. #92

New issue

Closed

opened 2017-10-26 02:04:07 +00:00 by jamie · 4 comments

jamie commented

2017-10-26 02:04:07 +00:00

(Migrated from git.hazaar.io)

Say we cache resources locally using the CDNJS view helper and one of these resources is a CSS file that links to another resource using a relative URL, such as a font file using an @import call or PNG image file using a url() method. The browser will attempt to obtain this file using the location of the CSS file as the URL base. However, because the 'base' is the same for ALL resources loaded via the CDNJS view helper, the requests will fail.

We need to come up with a method that allows a library to be referenced via the URL so that relative URLs will also work. This may mean that we can no longer use the encoded query string to load resources and may have to revert to the traditional path method. This could potentially be harmful as it could possibly allow anyone to load a resource through the site, allowing it to be cached and hence increasing traffic. We will need to have protections in place to prevent this. I'm thinking a start may be a local index of files that have been linked so that we know we are allowed to provide access to them.

Say we cache resources locally using the CDNJS view helper and one of these resources is a CSS file that links to another resource using a relative URL, such as a font file using an ```@import``` call or PNG image file using a ```url()``` method. The browser will attempt to obtain this file using the location of the CSS file as the URL base. However, because the 'base' is the same for ALL resources loaded via the CDNJS view helper, the requests will fail. We need to come up with a method that allows a library to be referenced via the URL so that relative URLs will also work. This may mean that we can no longer use the encoded query string to load resources and may have to revert to the traditional path method. This could potentially be harmful as it could possibly allow anyone to load a resource through the site, allowing it to be cached and hence increasing traffic. We will need to have protections in place to prevent this. I'm thinking a start may be a local index of files that have been linked so that we know we are allowed to provide access to them.

jamie commented

2017-10-26 02:04:11 +00:00

(Migrated from git.hazaar.io)

created branch 92-updates-to-handle-linked-relative-resources-when-using-cdnjs-local-cache-option

created branch [`92-updates-to-handle-linked-relative-resources-when-using-cdnjs-local-cache-option`](https://git.hazaarlabs.com/hazaar/hazaar-mvc/compare/master...92-updates-to-handle-linked-relative-resources-when-using-cdnjs-local-cache-option)

jamie commented

2017-10-26 02:04:13 +00:00

(Migrated from git.hazaar.io)

mentioned in merge request !9