Skip to content

overridable forbidden characters - #460

Open
DBLaci wants to merge 3 commits into
ankitpokhrel:mainfrom
AventailLtd:forbidden-character-list-setting
Open

DBLaci wants to merge 3 commits into
ankitpokhrel:mainfrom
AventailLtd:forbidden-character-list-setting

Conversation

@DBLaci

@DBLaci DBLaci commented Oct 29, 2025

Copy link
Copy Markdown

Some forbidden characters are in fact not invalid on either Windows or Linux. At least, it’s debatable whether these should be restricted at the library level. For example, the "&" character is commonly used in filenames by our users, so as the least drastic change, I’ve made this forbidden character list optionally overridable. Since this is not mandatory, it doesn’t break any existing functionality.

Thank you for your work, consider merging this PR

Several method signatures declared a typed parameter with a null
default (e.g. `string $key = null`) without the explicit `?` nullable
marker, which PHP 8.4 deprecates. Under environments with
display_errors on, the deprecation notices get echoed into the HTTP
response body before the real tus response headers/status are sent,
breaking the response (falls back to a bare 200).
…eStore::lock()

Missed in the previous pass because it's only exercised via the
FileStore cache backend, not RedisStore.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant