发表新帖
发表新帖

W7 Pro IIS 7.5 overwrites PHP Location: Header

前端 未结
关注
3 498
日久生厌
日久生厌 2021-01-05 18:30

I am creating a RESTful API in PHP, and have encountered a problem. When the client is posting data to the server, the server should return:

Status code 201
相关标签:
3条回答
  • 南方客
    2021-01-05 18:53

    The solution was to create an IIS module, that rewrites the header "Custom-Location" to "Location" after FastCGI is done.

    Then, FastCGI won't know that we are sending a Location header at all, and it won't modify my response.

    The module:

    string Location = context.Response.Headers["Custom-Location"] as string;
if (!string.IsNullOrEmpty(Location))
{
    context.Response.Headers.Remove("Custom-Location");
    context.Response.AddHeader("Location", Location);
}

    PHP:

    header("Custom-Location: http://google.no",true,201);
header("Content-Type: application/xml");
echo "<xml></xml>";

    (still dummy code, not extremly correct code :) )

    0 讨论(0)
  • 青春惊慌失措
    2021-01-05 18:58

    I had similar problem with WP REST API on IIS 8.5. Following html

    <head>
    <title>Document Moved</title>
</head>
<body>
    <h1>Object Moved</h1>
    This document may be found 
    <a HREF="[url-from-location-header]">here</a>
</body>

    was added at start of every json returned with Location header and status 201 Created. Content-Type was changed to text/html; charset=UTF-8.

    Adding cgi.rfc2616_headers = 1 in php.ini resulted with:

    • clean body (json) without added html
    • correct "Content-Type"
    • "Location" header missing
    • Status chaged to 200 OK

    I wouldn't call this solution, this is more replacing one problem with another. Luckily this new problem in my situation was smaller than original one.

    0 讨论(0)
  • 醉话见心
    2021-01-05 19:07

    I am sorry to bear bad news, but look here:

    Prevent IIS from changing response when Location header is present

    Edit: Never did find an answer - I ended up switching to Apache

    And it seems IIS has had its fingers into headers for a long time:

    http://forums.iis.net/t/1158431.aspx

    This is a bug in IIS FastCGI module. It will be fixed in Windows 7 RTM. We are also looking into possible ways for making this fix available for IIS 7.

    Hopefully if the bugs are related (I expect they are), if you now have FastCGI, then the fix below could work. Otherwise, switching to PHP non-FastCGI module might also work, and it might be easier than throwing in with Apache.

    http://support.microsoft.com/kb/980363

    0 讨论(0)
 看不清?
提交回复
热议问题