Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago
Solved

x-ms-continuationtoken not available in header information

Hi there, 

I am trying to create a report like this.

But my Power BI desktop seems to not return the whole header information. I get only the "Content-Type", if I return the whole header.

(Azure DevOps Server 2019 Update 1)

 

let
    URL = "https://devopsurl.int/tfs/collection/project/_apis/build/builds?api-version=5.1&$top=100",
    Content = Web.Contents(URL),
    AsJson = Json.Document(Content),
    headerdata = Value.Metadata(Content)[Headers]?

in
    headerdata

 

 

headerdata:

 

Content-Type: application/json; charset=utf-8; api-version=5.1

 

 

If i paste the URL in Firefox, it shows the header information as following:

 

ActivityId: XXXXXXXXXXXXXXXXXXXXXXXXXXXX
Cache-Control: no-cache
Content-Encoding: gzip
Content-Length: 50235
Content-Type: application/json; charset=utf-8; api-version=5.1
Date: Tue, 19 Jan 2021 11:19:43 GMT
Expires: -1
Lfs-Authenticate: NTLM
P3P: CP="XXX XXX XXX XXX XXX XXX XXX XXX XXX"
Persistent-Auth: true
Pragma: no-cache
Vary: Accept-Encoding
X-Content-Type-Options: nosniff
X-FRAME-OPTIONS: SAMEORIGIN
X-Powered-By: ASP.NET
...
x-ms-continuationtoken: 2019-04-30T09:33:19.2354372Z

.....

 

 

Why is it not possible for PowerBI to get those header information, especially the continuationtoken?

Need Help
  • Anonymous's avatar
    Anonymous
    5 years ago

    Anonymous 
    It is not support, please refer to the solution from HTTP response headers in metadata (microsoft.com).

    "Hi Chris. It comes down to security. We limit the headers you're allowed to read to prevent someone from being able to construct a malicious query that reads a user's auth-related header values. We also restrict the header values you're allowed to generate to prevent the possibility of PQ being used for session hijacking."


    Paul Zheng _ Community Support Team
    If this post helps, please Accept it as the solution to help the other members find it more quickly.

1 Reply

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    Anonymous 
    It is not support, please refer to the solution from HTTP response headers in metadata (microsoft.com).

    "Hi Chris. It comes down to security. We limit the headers you're allowed to read to prevent someone from being able to construct a malicious query that reads a user's auth-related header values. We also restrict the header values you're allowed to generate to prevent the possibility of PQ being used for session hijacking."


    Paul Zheng _ Community Support Team
    If this post helps, please Accept it as the solution to help the other members find it more quickly.