archive
/
matrix-spec
mirror of https://github.com/matrix-org/matrix-spec
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update proposals/1884-replace-slashes-in-event_ids.md

Browse Source 
Co-Authored-By: ara4n <matthew@arasphere.net>
pull/977/head
Hubert Chathi 6 years ago committed by GitHub
parent 207d6cf851
commit 9dcf2d6a28
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File

4
proposals/1884-replace-slashes-in-event_ids.md
Unescape Escape View File

@ -27,7 +27,7 @@ of reasons:
* Even if client implementations do remember to URL-encode their parameters, * Even if client implementations do remember to URL-encode their parameters,
they may not do it correctly: many URL-encoding implementations may be they may not do it correctly: many URL-encoding implementations may be
intended to encode parameters in the query-string (which can of course intended to encode parameters in the query-string (which can of course
contain literal slashes) rather tha the path component. contain literal slashes) rather than the path component.
* Some proxy software may treat `%2F` specially: for instance, Apache, when * Some proxy software may treat `%2F` specially: for instance, Apache, when
configured as a reverse-proxy, will reject requests for a path containing configured as a reverse-proxy, will reject requests for a path containing
@ -162,4 +162,4 @@ it feels we should not prioritise consistency of encodings for SS/E2EE developer
over the usability of the CS API. over the usability of the CS API.
Therefore, on balance, it seems plausible that changing the format of event IDs Therefore, on balance, it seems plausible that changing the format of event IDs
does solve sufficient problems to make it desirable. does solve sufficient problems to make it desirable.

Write Preview
Loading…
Cancel
Save