Search Issue Tracker
Fixed in 2018.4.3f1
Fixed in 2018.4.X, 2019.1.X, 2019.2.X
Votes
1
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.1.0f2
2019.2.0a1
2019.3.0a1
Issue ID
1151016
Regression
No
[UnityWebRequest] UnityWebRequest.EscapeURL ignores specified encoding when creating the URL
How to reproduce:
1. Open the attached project ("case_1151016-WebRequestEscapeURL")
2. Open the repro scene ("SampleScene")
3. Enter Play Mode
4. Inspect Console
Expected results: EscapeURLs created with and without encoding are different
Actual results: EscapeURLs are the same no matter which encoding is used (or none at all)
Reproducible with: 2017.4.26f1, 2018.4.0f1, 2019.1.2f1, 2019.2.0a14, 2019.3.0a2
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 2018.4.3f1):
Fixed in 2018.4.3f1, 2019.1.4f1, 2019.2.0b3, 2019.3.0a3