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

Co-Authored-By: ara4n <matthew@arasphere.net>
This commit is contained in:
Hubert Chathi 2019-04-01 00:43:31 +01:00 committed by GitHub
parent 207d6cf851
commit 9dcf2d6a28
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

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