1056339 - IndexedDB fails to open a database if the URL is too long

Status: RESOLVED DUPLICATE of bug 1536796

(Core :: Storage: IndexedDB, defect, P5)

Description

[Marco Castelluccio [:marco]]

Attachment: indexeddb.html

Looks like IndexedDB.open fails if the URL is > 255 characters.

Comment 1

[Marco Castelluccio [:marco]]

I think this only happens with the file:// protocol

Comment 2

[Andrew Overholt [:overholt]]

Is this related to bug 1166060?

Comment 3

[Marco Castelluccio [:marco]]

Definitely sounds similar, but I can't tell if fixing bug 1166060 would fix this as well.

Comment 4

[Jan Varga [:janv]]

(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.

Comment 5

[Andrew Sutherland [:asuth] (he/him)]

I believe bug 1536796 (and its follow-ups) addressed problems with file paths that are too long on windows for QM/IDB by having us using \\.\ magic to escape the windows path restrictions.