Open
Bug 84045
Opened 23 years ago
Updated 8 months ago
imap uris are not properly escaped (in localstore.rdf, prefs.js, filters, migration code)
Categories
(MailNews Core :: Backend, defect)
MailNews Core
Backend
Tracking
(Not tracked)
NEW
People
(Reporter: sspitzer, Unassigned)
References
(Blocks 3 open bugs, )
Details
spun off from bug #83980
imap uris (in localstore.rdf) are not properly escaped
create a folder on an imap account with a space, and do the same on a local
account. then, give those folders children folders and expand them. (expanded
state shows up in localstore.rdf)
when you look at your localstore.rdf after quitting, you'll see something like
this:
<NC:persist resource="imap://sspitzer@nsmail-1.mcom.com/Foo And Cheese"/>
<NC:persist resource="mailbox://nobody@Local%20Folders/Beer%20and%20Wine"/>
uri's should be in escaped UTF-8. the local case is right, imap is wrong.
I'm not sure where (or if) this is causing us problems.
but putting it on the radar to investigate.
Reporter | ||
Comment 1•23 years ago
|
||
I'm also worried that we might not be properly escaping the uri internally.
just getting this down into bugzilla for investigation later.
Reporter | ||
Comment 2•23 years ago
|
||
see 100854 for related issues.
Depends on: 100854
Summary: imap uris (in localstore.rdf) are not properly escaped? → imap uris are not properly escaped (in localstore.rdf, prefs.js, filters, migration code)
Updated•23 years ago
|
QA Contact: esther → huang
Updated•20 years ago
|
Product: MailNews → Core
Updated•19 years ago
|
Blocks: folders-with-special-characters
Comment 3•17 years ago
|
||
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
Updated•17 years ago
|
OS: Other → All
QA Contact: huang → backend
Hardware: Other → All
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
This seems to still exist, but the paths are in the file folderTree.json (for TB).
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•