Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0b7
Issue ID
917097
Regression
Yes
ArgumentException: Cannot set Request Header when trying to upload to Firebase Storage
ArgumentException: Cannot set Request Header Content-Length - name contains illegal characters or is not user-overridable
How to reproduce:
1. Open user attached project
2. Enter playmode
Expected behaviour: Successful attempt to send files to Firebase (404 since we don't have access)
Actual behaviour: Argument exception
Regression introduced in: 2017.1.0b1
Reproduced on: 2017.1.0b1, 2017.1.0b5, 2017.1.0b8, 2017.2.0a2
Not reproduced on: 5.5.4f1, 5.6.2p2
Full error from 2017.1.0b1:
ArgumentException: Cannot set Request Header Content-Length - name contains illegal characters or is not user-overridable
UnityEngine.Networking.UnityWebRequest.SetRequestHeader (System.String name, System.String value) (at C:/buildslave/unity/build/artifacts/generated/common/modules/UnityWebRequest/WebRequestBindings.gen.cs:473)
UnityEngine.WWW..ctor (System.String url, System.Byte[] postData, System.Collections.Generic.Dictionary`2 headers) (at C:/buildslave/unity/build/Runtime/WebRequestWWW/UWRWWW.cs:60)
Firebase.Unity.WWWHttpRequest+<SendUnityRequest>c__Iterator0.MoveNext ()
UnityEngine.SetupCoroutine.InvokeMoveNext (IEnumerator enumerator, IntPtr returnValueAddress) (at C:/buildslave/unity/build/Runtime/Export/Coroutines.cs:17)
UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
Firebase.Unity.UnitySynchronizationContext:<PostCoroutine>m__0(Object)
Firebase.Unity.<Start>c__Iterator0:MoveNext()
UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
xXLioXx
Dec 23, 2017 11:43
Hello.
Is there any news about that ? I'm having the same problem (under 2017.2.0.f3)
thx