whether it's incorrect or not, keeping around a feature for a rarely-used requirement of sentinels within the path is not helpful in a world where url construction is happening in code, with user-configured values, etc.
I'd rather have the "incorrect" behavior from nginx than try to track down arbitrary 404s due to bodged url construction, any day.
whether it's incorrect or not, keeping around a feature for a rarely-used requirement of sentinels within the path is not helpful in a world where url construction is happening in code, with user-configured values, etc.
I'd rather have the "incorrect" behavior from nginx than try to track down arbitrary 404s due to bodged url construction, any day.