--- title: Support for Client Reporting over HTTP description: Support for Client Reporting over HTTP author: manikadhiman ms.assetid: 4a26ac80-1fb5-4c05-83de-4d06793f7bf2 ms.reviewer: manager: dansimp ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 ms.date: 08/30/2016 --- # Support for Client Reporting over HTTP Version 4.6 of the App-V client now supports the use of HTTP communication when sending client reporting data to the publishing server. This feature supports scenarios where a customer has implemented a custom HTTP(S) publishing server that is configured to collect and process client data. For more information on HTTP publishing servers, see ## Client Reporting over HTTP The client starts collecting data when it receives a “REPORTING=”TRUE””attribute in the publishing refresh response XML from the publishing server. When this attribute is received, the client sends any accumulated data to the publishing server that sent the publishing refresh. The details of this process are as follows: - The client sends an HTTP GET request to the publishing server for a publishing refresh. The header of this message contains an “AppV-Op:Refresh” custom header that the custom HTTP(S) publishing server uses to identify the message type. - The publishing server then sends the publishing refresh response XML that contains a “REPORTING=”TRUE”” value. - The client then sends an HTTP POST request to the publishing server along with the reporting data that has been gathered since the previous refresh. The header of this message contains an “AppV-Op:Report” custom header that the custom HTTP(S) publishing server uses to identify the message type. The following schema gives specific details of the package and the application data that is sent to the server. ```xml ```