Search Unity

  1. Curious about what's going to be in 2020.1? Have a look at the 2020.1 beta blog post.
    Dismiss Notice
  2. Want to see 2020.1b in action? Sign up for our Beta 2020.1 Overview Webinar on April 20th for a live presentation from our evangelists and a Q&A session with guests from R&D.
    Dismiss Notice
  3. Interested in giving us feedback? Join our online research interviews on a broad range of topics and share your insights with us.
    Dismiss Notice
  4. New Unity Live Help updates. Check them out here!

    Dismiss Notice

WWW exception in 2017.1 but not 5.6

Discussion in '2017.1 Beta' started by peteradvr, Jun 14, 2017.

  1. peteradvr


    Dec 22, 2016
    The following code used to work great in 5.5 and 5.6 but is now throwing an exception in 2017.1. I'm trying to figure out if I'm just fundamentally doing something wrong that happened to work in 5.6 but now fails in 2017.1 or if this is a Unity bug.

    private static readonly string contentType = "Content-Type";
    private static readonly string contentLength = "Content-Length";

    internal static WWW PostJsonToURL(string uploadText, string postURL)
    System.Text.UTF8Encoding encoding = new System.Text.UTF8Encoding();
    Dictionary<string, string> postHeader = new Dictionary<string, string>();

    postHeader.Add(contentType, "text/json");
    postHeader.Add(contentLength, uploadText.Length.ToString());

    WWW request = new WWW(postURL, encoding.GetBytes(uploadText), postHeader);
    return request;

    when I run this in 2017.1 I get this exception in the WWW constructor:

    InvalidOperationException: Cannot override system-specified headers
    UnityEngine.Networking.UnityWebRequest.SetRequestHeader (System.String name, System.String value) (at C:/buildslave/unity/build/artifacts/generated/common/modules/UnityWebRequest/WebRequestBindings.gen.cs:471)
    UnityEngine.WWW..ctor (System.String url, System.Byte[] postData, System.Collections.Generic.Dictionary`2 headers) (at C:/buildslave/unity/build/Runtime/WebRequestWWW/UWRWWW.cs:62)

    Any advice?
  2. Dustin-Horne


    Apr 4, 2013
    My guess is that it's not allowing you to override the Content-Length header. It's probably setting that automatically internally (as it really should be anyway).
  3. Aurimas-Cernius


    Unity Technologies

    Jul 31, 2013
    In 2017.1 WWW class was rewritten to be a wrapper on top of UnityWebRequest. This imposes a more strict rules for headers you can set, specifically not allowing to set headers that are either set automatically of can cause problems.
    The Content-Type is set automatically to correct value and should not be set manually. Even in old WWW implementation setting this header was asking for trouble.
    ShahSoft and Dustin-Horne like this.
  4. peteradvr


    Dec 22, 2016
    Thanks for the help. That worked. Removing Content-Length fixed my issue.
    ShahSoft, guetta18 and Dustin-Horne like this.