With reference to This question, and ScottGu’s Documentation, I have successfullr routed a Url for my sites’ Member profile page.
My page redirects ~/page/MemberName to ~/page/Default.aspx, which users the MemberName to request info.
This has worked fine until now.
I need a way to now allow a user to edit their data, and would like it to be accessed like ~/page/MemberName/Private. The Private tag will tell the page the user can edit their content.
While I would consider doing what @huMpty duMpty suggests and using Roles for this.
You just need to set up your route to contain extra information in the URL.
And then access it just like you would MemberName:
If you want to make sure that only ‘Private’ is ever passed in you can add constraints to the route via one of the overloads.
It’s worth noting that you may want to test this pretty well as you might end up with an overly strict routing rule.