You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this case, trying to render index.jade will give an exception. The reason is that the include is parsed by taking the filename String used to create the parser for index.jade is translated to a URI using the method URI.create [Parser:313], which is assumed to accept only strictly legal URI string (ie. no spaces). The filename string used to create the parser for index.jade however, is passed (ultimately) to the constructor of a File object [FileTemplateLoader:37].
A quick fix would be to use new URI(...) in Parser:313, so the filename path is escaped. I think ultimately you may need to make a more consistent decision about how template paths are stored (eg. store them as URIs always, and use the 'file://' prefix for local files).
The text was updated successfully, but these errors were encountered:
Consider the following situation:
In this case, trying to render index.jade will give an exception. The reason is that the include is parsed by taking the filename String used to create the parser for index.jade is translated to a URI using the method URI.create [Parser:313], which is assumed to accept only strictly legal URI string (ie. no spaces). The filename string used to create the parser for index.jade however, is passed (ultimately) to the constructor of a File object [FileTemplateLoader:37].
A quick fix would be to use new URI(...) in Parser:313, so the filename path is escaped. I think ultimately you may need to make a more consistent decision about how template paths are stored (eg. store them as URIs always, and use the 'file://' prefix for local files).
The text was updated successfully, but these errors were encountered: