{"_id":"57e46e50fe6af90e002ed536","__v":0,"initVersion":{"_id":"545137a814af501a00b50cfc","version":"1.0"},"project":"545137a814af501a00b50cf9","user":{"_id":"5638f69b22afbc0d001f23c1","username":"","name":"Yammer Platform DL"},"createdAt":"2016-09-22T23:50:40.131Z","changelog":[],"body":"The Yammer infrastructure team has made a recent change which may affect your use of the Yammer REST API. As part of a Microsoft-wide effort, Yammer has onboarded the vast majority of traffic to an Azure-based, global load-balancing platform used across O365.This provides improved security, compliance, and DDOS protection for Yammer. It brings technology from the Windows kernel and IIS HTTP request handling system including:\n\n1) http.sys: https://support.microsoft.com/en-us/kb/820129\n\n2) IIS: https://www.iis.net/configreference/system.webserver/security/requestfiltering/requestlimits\n\nAs a result, all Yammer REST API calls and requests have to comply with IIS and http.sys requirements which may be stricter than the requirements previously in place, and include items which are considered optional within the HTTP specification. Most developers will not need to make any changes, because underlying HTTP libraries already send requests that are compliant. Please review the structure of your HTTP requests for compliance if you receive 4xx or 5xx errors from Yammer. \n\nAn example requirement is for requests to have a Content-Length header. Make sure that you specify *Content-Length: 0* for requests that do not have a body, or they may be rejected.\n\nWe hope this transition is a smooth one for your Yammer app/integration. If you have any questions, please use one of these Support channels: https://developer.yammer.com/v1.0/page/support.","slug":"action-required-comply-with-iis-and-httpsys","title":"Action Required: Comply with IIS and http.sys"}

Action Required: Comply with IIS and http.sys


The Yammer infrastructure team has made a recent change which may affect your use of the Yammer REST API. As part of a Microsoft-wide effort, Yammer has onboarded the vast majority of traffic to an Azure-based, global load-balancing platform used across O365.This provides improved security, compliance, and DDOS protection for Yammer. It brings technology from the Windows kernel and IIS HTTP request handling system including: 1) http.sys: https://support.microsoft.com/en-us/kb/820129 2) IIS: https://www.iis.net/configreference/system.webserver/security/requestfiltering/requestlimits As a result, all Yammer REST API calls and requests have to comply with IIS and http.sys requirements which may be stricter than the requirements previously in place, and include items which are considered optional within the HTTP specification. Most developers will not need to make any changes, because underlying HTTP libraries already send requests that are compliant. Please review the structure of your HTTP requests for compliance if you receive 4xx or 5xx errors from Yammer.  An example requirement is for requests to have a Content-Length header. Make sure that you specify *Content-Length: 0* for requests that do not have a body, or they may be rejected. We hope this transition is a smooth one for your Yammer app/integration. If you have any questions, please use one of these Support channels: https://developer.yammer.com/v1.0/page/support.