Open
Bug 1056339
Opened 10 years ago
Updated 2 years ago
IndexedDB fails to open a database if the URL is too long
Categories
(Core :: Storage: IndexedDB, defect, P5)
Tracking
()
NEW
People
(Reporter: marco, Unassigned)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
450 bytes,
text/html
|
Details |
Looks like IndexedDB.open fails if the URL is > 255 characters.
Reporter | ||
Comment 1•10 years ago
|
||
I think this only happens with the file:// protocol
Reporter | ||
Comment 3•9 years ago
|
||
Definitely sounds similar, but I can't tell if fixing bug 1166060 would fix this as well.
Flags: needinfo?(mcastelluccio)
Updated•7 years ago
|
Priority: -- → P5
Comment 4•5 years ago
|
||
(In reply to Marco Castelluccio [:marco] from comment #3)
Definitely sounds similar, but I can't tell if fixing bug 1166060 would fix
this as well.
Yeah, that bug is now fixed and helped a lot, but I think we can still hit the MAX_PATH, if the HTML file is stored very deeply in the directory structure:
<profile>/storage/default/file++++Users+foo+subdir1+subdir2+subdir3+subdir4+subdir5+(more subdirs)+index.html
We need to replace the long origin directory name (taken from the File URL spec) with a unique (fixed size) name and store the mapping in a database.
Depends on: 1593365
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•