Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.2.X
Votes
0
Found in
2020.1.0a12
2020.3
2020.3.15f2
2021.1
2021.2
2022.1
Issue ID
1355007
Regression
Yes
Warning is logged when using UnityWebRequest to set the header to Accept-Encoding
Reproduction steps:
1. Open the attached "TestAcceptEncodingProject.zip" project
2. Enter Play Mode
3. In Game view, click the "Push To Call SetRequestHeader" button
Expected result: No warning in the Console or a way to disable the warning from being logged
Actual result: Console logs a warning ("The header Accept-Encoding is managed automatically, setting it may have no effect or result in unexpected behavior")
Reproducible with: 2020.1.0a12, 2020.3.15f2, 2021.1.16f1, 2021.2.0b6, 2022.1.0a4
Not reproducible with: 2018.4.36f1, 2019.4.29f1, 2020.1.0a11
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 2022.1):
Fixed in 2022.1.0b1: The warning is no longer being logged
Resolution Note (fix version 2021.2):
Fixed in 2021.2.6f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.25f1