WinHTTP and UNSAFE_HEADER_PARSING, Where is it? RRS feed

  • Question

  • Per the following KB...

    I confirmed that I am getting this problem on a Server2008, and not on an XP machine.  So I intend to attempt this fix.

    The fix installed fine, the build versions are correct.  But...

    What is the value of the new option: WINHTTP_OPTION_UNSAFE_HEADER_PARSING?? It's not documented anywhere, and obviously is not in the SDK headers.

    I can't actually use this hotfix if the option value is not documented anywhere.


    • Moved by Jesse Jiang Friday, November 12, 2010 3:30 AM (From:Visual C++ General)
    Wednesday, November 10, 2010 4:19 PM

All replies

  • Well it's kinda bizarre that the flag's value is not documented anywhere. I don't have the hotfix (it's not easy to download it, you need to fill in a request form and then they contact you and stuff). But perhaps the hotfix download includes some document with this info?
    Wednesday, November 10, 2010 4:38 PM
  • I used the feedback form on that KB article and told them that without mentioning what WINHTTP_OPTION_UNSAFE_HEADER_PARSING needs to be #define'd as, the content in the article is unusable. Hopefully someone will see that and update the information in the article.
    Wednesday, November 10, 2010 4:45 PM
  • I used the same feedback form.  Not that I expect any results.  History has taught me not to.

    I confirmed that the problem occurs when a header name has a semicolon.  Semicolons in values work just fine.  (the problem descritption is not even clear on that).  As for the fix, it is installed on a Server 2008.  The build numbers are now current, and the problem is still ocurring... because I can't set the new option.

    I can't install the fix on my XP machine, and I can't just install the entire dev environment on this server.

    The extent of the fix was to replace two DLLs, and provide nothing else.  I even downloaded a TypeLib viewer and examined the WinHTTP type lib on the server.  There are no new enumerated options listed in it.  And there are two different fixes, one for Win 7, and one for Server2008.

    I have a customer experiencing this *right now* and I have to tell them... what?  That MS won't provide adequate help?  That they need to go tell their behemoth size server company to fix their web page because of one tiny server in one small customer installation?

    Ah well.  This is why I keep trying to get out of software development...


    Friday, November 12, 2010 1:26 PM
  • Another week...  Still nothing from MS.
    Wednesday, November 17, 2010 2:19 PM
  • Tick...  Tick...  Tick...

    Does no one at MS care about their customers?

    Is there an MVP out there who has done this in WIN32?

    Tuesday, November 30, 2010 1:41 PM