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
our current redirect architecture is focussed on being able to produce very fast 404 for independent security researchers and we should definitely keep it that way. for extensionless requests, i think we could support pattern based redirects without significant extra overhead and they could work from a precedence standpoint below actual content...
we would have to discuss how flexible we would like the patterns to be (should they be similar to what we use in metadata) and probably we also need to discuss how to use variables in templates, which i think ideally should be the same in other places. eg. potentially templated metadata
The text was updated successfully, but these errors were encountered:
@davidnuescheler from an authoring point of view, we are in support of pattern/variables or anything that will help us reduce the number of 1:1 redirects and overall content management pain points in spreadsheets. Wondering if there's any information we can provide to help make this enhancement a reality.
our current redirect architecture is focussed on being able to produce very fast
404
for independent security researchers and we should definitely keep it that way. for extensionless requests, i think we could support pattern based redirects without significant extra overhead and they could work from a precedence standpoint below actual content...(1) explicit redirect
(2) content
(3) pattern redirect
we would have to discuss how flexible we would like the patterns to be (should they be similar to what we use in metadata) and probably we also need to discuss how to use variables in templates, which i think ideally should be the same in other places. eg. potentially templated metadata
The text was updated successfully, but these errors were encountered: