5f7321dcc7
When unmounting, the router entry would be tainted, preventing routing. However, we would then unmount the router before clearing storage, so if an error occurred the router would have forgotten the path. For auth mounts this isn't a problem since they had a secondary check, but regular mounts didn't (not sure why, but this is true back to at least 0.2.0). This meant you could then create a duplicate mount using the same path which would then not conflict in the router until postUnseal. This adds the extra check to regular mounts, and also moves the location of the router unmount. This also ensures that on the next router.Mount, tainted is set to the mount entry's tainted status. Fixes #6769 |
||
|---|---|---|
| .. | ||
| api | ||
| identity | ||
| misc | ||
| policy | ||
| response | ||
| router | ||
| token | ||