I agree that in this example, the user does have permission when the
user logs in. The same might be true with 403 where the user needs to
login or login using a different Launchpad profile.
Both launchpad-forbidden.pt and launchpad-notfound.pt should state:
You may need to login as a different to access this URL.
** Summary changed:
- 404 on private objects is confusing
+ 404 page for private objects is confusing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/777797
Title:
404 page for private objects is confusing
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/777797/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
