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
- A script cannot be attached to a GameObject when there is another script that is generic with the same name in a different folder
- Scene View drop-down fields reopen when clicking them again to close it
- Crash on UnityEngine.Rendering.RenderPipelineAsset:InternalCreatePipeline when opening a specific project
- [STW 6.1] UI Builder Inspector fields get corrupted when docked UI Builder is maximized
- Pickers and ‘+'/’-' buttons are not visible on the right side of parameter fields when the width of the "Project Settings... -> Quality" window is small
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