locked
Http Request-Response - Custom Header RRS feed

  • Question

  • Team

    Bit odd request and question, but somehow the vendor we connect with is not wanting to have those custom x-ms-* headers that are generated.

    We have logic app doing AS2/B2B scenario and for one of the vendor we generate "Synchronous MDN".   MDN itself ( along with outbound header generated by MDN and the content ) are perfectly fine, although at the time when HTTP syncrhonous Response is sent out, below are the additional Headers that are added, which seems to be troublesome for processing MDN for the vendor!

    x-ms-execution-location: centralus

    x-ms-workflow-id: 

    x-ms-workflow-version: 

    x-ms-workflow-name: InboundAs2

    x-ms-workflow-run-id: 

    x-ms-workflow-system-id: /locations/centralus/....

    x-ms-tracking-id: 39276a0d-cb15-4c5f-b104-94a3d5f474a3

    x-ms-correlation-id: 39276a0d-cb15-4c5f-b104-94a3d5f474a3

    x-ms-client-tracking-id: 08587241139871062948787946432

    x-ms-ratelimit-remaining-workflow-writes: 250000

    x-ms-ratelimit-burst-remaining-workflow-writes: 40000

    x-ms-request-id: centralus:39276a0d-cb15-4c5f-b104-94a3d5f474a3

    Strict-Transport-Security: max-age=31536000; includeSubDomains

    Do we have option available we we can ignore "specific custom header" or not generate those ( I know that option probably is available via some sort of config file in API )

    Thanks

    Ashish

    Friday, October 28, 2016 9:58 PM

Answers

  • Hello Ashish,

    Disabling system generated header is not possible today and this is something not on our current road map ether. But we are always re-evaluating our backlog & plans based on customer feedback, so please submit / vote for the idea on user voice:

    Regards,

    Raj

    • Proposed as answer by Rajshekher-BT Tuesday, November 1, 2016 12:41 AM
    • Marked as answer by Sjoukje ZaalMVP Thursday, March 16, 2017 9:56 AM
    Tuesday, November 1, 2016 12:10 AM

All replies

  • Hello Ashish,

    Disabling system generated header is not possible today and this is something not on our current road map ether. But we are always re-evaluating our backlog & plans based on customer feedback, so please submit / vote for the idea on user voice:

    Regards,

    Raj

    • Proposed as answer by Rajshekher-BT Tuesday, November 1, 2016 12:41 AM
    • Marked as answer by Sjoukje ZaalMVP Thursday, March 16, 2017 9:56 AM
    Tuesday, November 1, 2016 12:10 AM
  • Perhaps, asking the same question as above. In a scenario where we are using Azure storage as origin for the Azure CDN for the purpose of serving static content, what is the utility of having all of these headers exposed on every single request? 

    For example, if you copy a blob from one container to another:

      HTTP/1.1 200 OK
      x-ms-request-id: 87458992-0001-0126-122b-748skjhkjs
      x-ms-version: 2015-12-11
      x-ms-lease-status: unlocked
      x-ms-lease-state: available
      x-ms-blob-type: BlockBlob
      x-ms-copy-id: abc984594-de79-4a0a-b99a-198435989aabcd
      x-ms-copy-source: https://XXXX.blob.core.windows.net/container/file.jpg?sv=2016-05-31&sr=b&sig=abcdefghtifkjsds%3D&se=2017-02-06T18%3A56%3A14Z&sp=r&api-version=2016-05-31
      x-ms-copy-status: success
      x-ms-copy-progress: 145237/145237
      x-ms-copy-completion-time: Mon, 30 Jan 2017 18:56:13 GMT
      x-ms-server-encrypted: false

    There's a lot of metadata that is unnecessarily verbose at best and at worst could possibly lead to leaking unwanted information.

    What can be done to prevent this?  Or is there a way to delete all of this?


    • Edited by MrGreg77 Monday, January 30, 2017 7:16 PM
    Monday, January 30, 2017 7:14 PM
  • We are starting to use Logic Apps in the business but finding that some of the headers that are appended to the HTTP request are causing issues with third party providers.

    I.e. When trying to post to loggly the headers: X-Ms-Workflow-System-Id, Cf-Visitorcause problems.

    There is no possibility to overwrite them on the Logic app designer/code view.

    Like MrGreg77 I think there is a lot of metadata included and some level of customization should be allowed, and most important the ability to remove some of them.

    This is not one case, I have found issues when doing simple post request with different REST APIs that are sucessful using POSTMAN due these added headers.



    • Edited by Eduardo GR Friday, January 19, 2018 10:59 AM removing tags
    Friday, January 19, 2018 10:56 AM