Bugzilla

(In reply to Robert Chapin from comment #22)
> Maybe I'm over-thinking this but why isn't it a simple matter of matching the profile path?  Then you wouldn't have to block anything.

The core intention here is really to confine mailbox URLs to only see files within that profile, I think?
I'd suspect matching arbitrary paths isn't _entirely_ trivial - you have to normalise the paths first (ie "foo/../bar/..." -> "bar/...") and handle percent-encoding and various other things - but I know it can be done.
That'd seem to be the "right" solution.

(ultimately, I think we need to kill off using raw paths in mailbox URLs entirely - it just seems like asking for trouble. mailbox URLS _should_ just be of the form: `mailbox:{server}/{folder}/msgKey`. But that's a bigger issue :- ).

(In reply to Magnus Melin [:mkmelin] from comment #18)
> Agreed In corporate environments it's common to have the user drive (really) mapped somewhere else, but I think those would be mapped to a drive so you can set it all up when you log on. Mapped drives would show as "normal" local file paths. 

I dunno... from a quick web search on "windows folder redirection" it kind of sounds like that's the way admin policy is supposed to be handled on windows these days... (I'm a bit out of touch with this stuff). And Folder Redirection shows up to us as UNC paths, so we need to support them robustly.

(In reply to Robert Chapin from comment #22)
> Maybe I'm over-thinking this but why isn't it a simple matter of matching the profile path?  Then you wouldn't have to block anything.

I think I agree: The core intention here is really to confine mailbox URLs to only see files within that profile, right?
I'd suspect matching arbitrary paths isn't _entirely_ trivial - you have to normalise the paths first (ie "foo/../bar/..." -> "bar/...") and handle percent-encoding and various other things - but I know it can be done.
That'd seem to be the "right" solution.

(ultimately, I think we need to kill off using raw paths in mailbox URLs entirely - it just seems like asking for trouble. mailbox URLS _should_ just be of the form: `mailbox:{server}/{folder}/msgKey`. But that's a bigger issue :- ).

(In reply to Magnus Melin [:mkmelin] from comment #18)
> Agreed In corporate environments it's common to have the user drive (really) mapped somewhere else, but I think those would be mapped to a drive so you can set it all up when you log on. Mapped drives would show as "normal" local file paths. 

I dunno... from a quick web search on "windows folder redirection" it kind of sounds like that's the way admin policy is supposed to be handled on windows these days... (I'm a bit out of touch with this stuff). And Folder Redirection shows up to us as UNC paths, so we need to support them robustly.