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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2018.4.3f1):
Fixed in 2018.4.3f1, 2019.1.4f1, 2019.2.0b3, 2019.3.0a3