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
The way the development server is invoked, it has no way to know what the url_path_prefix is. It's mostly fine, but it causes incorrect behavior in the following scenario.
Have a site with a url_path_prefix with the value prefix. Create an index page, that does a $link.page('foo'). It can be accessed at localhost:<port>/ (not localhost:<port>/prefix/). When zine built the page, $link.page('foo') resolved to /prefix/foo (which makes sense). But now, there's a link that points to localhost:<port>/prefix/foo, which is not where the development server is serving the page.
I think this should be solved by simply passing the url_path_prefix as an argument to the development server and serving it with that prefix. The only problem that would introduce is that now nothing is served at localhost:<port>. Maybe it could return a 301 moved permanently to redirect to localhost:<port>/prefix, for convenience?
The text was updated successfully, but these errors were encountered:
The way the development server is invoked, it has no way to know what the
url_path_prefix
is. It's mostly fine, but it causes incorrect behavior in the following scenario.Have a site with a
url_path_prefix
with the valueprefix
. Create anindex
page, that does a$link.page('foo')
. It can be accessed atlocalhost:<port>/
(notlocalhost:<port>/prefix/
). When zine built the page,$link.page('foo')
resolved to/prefix/foo
(which makes sense). But now, there's a link that points tolocalhost:<port>/prefix/foo
, which is not where the development server is serving the page.I think this should be solved by simply passing the
url_path_prefix
as an argument to the development server and serving it with that prefix. The only problem that would introduce is that now nothing is served atlocalhost:<port>
. Maybe it could return a301 moved permanently
to redirect tolocalhost:<port>/prefix
, for convenience?The text was updated successfully, but these errors were encountered: