[wp-trac] [WordPress Trac] #63780: [core] Upgrades over FTP fail for files owned by users or groups with space in the name (non-Windows systems)
WordPress Trac
noreply at wordpress.org
Thu Aug 28 22:50:47 UTC 2025
#63780: [core] Upgrades over FTP fail for files owned by users or groups with space
in the name (non-Windows systems)
-----------------------------+------------------------------
Reporter: ivucica | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Upgrade/Install | Version: 6.8.2
Severity: normal | Resolution:
Keywords: | Focuses: administration
-----------------------------+------------------------------
Comment (by ivucica):
Looks like that might do the trick, if the server supports RFC 3659 (March
2007).
The 'facts' in MLSD seem to be composed of SCHARs:
{{{#!php
RCHAR = ALPHA / DIGIT / "," / "." / ":" / "!" /
"@" / "#" / "$" / "%" / "^" /
"&" / "(" / ")" / "-" / "_" /
"+" / "?" / "/" / "\" / "'" /
DQUOTE ; <"> -- double quote character (%x22)
SCHAR = RCHAR / "=" ;
}}}
and example of the traffic from the RFC:
{{{#!php
C> MLSD
S> 150 I tink I tee a trisector tree
D> Type=file;Unique=aaab8cUYqaaa;Perm=rf;Size=15039; list.c
D> Type=pdir;Unique=aaaaacUYqaaa;Perm=cpmel; /
D> Type=pdir;Unique=aaaaacUYqaaa;Perm=cpmel; ..
D> Type=file;Unique=aaab8bUYqaaa;Perm=rf;Size=34589; ftpd.c
D> Type=cdir;Unique=aaab8aUYqaaa;Perm=cpmel; /files
S> 226 That's all folks...
}}}
It feels it's differently underspecified, given that facts seem to be
prohibited from many characters -- including, amusingly, whitespace. RFC
mainly talks about encodings such as UTF-8 in context of pathnames
themselves; this might be fine.
But if the server supports it, this does seem to be more correct, and if
not, PHP core would need to solve it.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/63780#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list