Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
When using Web.Contents URLs over 2000ish characters in length have resulted in an error:
"The underlying connection was closed: the connection was closed unexpectedly"
Is this error caused by the length of the URL?
Solved! Go to Solution.
@Anonymous,
I haven't found any infomation about maximum URL for Web.Contents() function. For OData.Feed() function, there is a MaxUriLength
property.
In your scenario, I would recommend you use Fiddler to track what is going on in the background.
Regards,
Lydia
@Anonymous,
I haven't found any infomation about maximum URL for Web.Contents() function. For OData.Feed() function, there is a MaxUriLength
property.
In your scenario, I would recommend you use Fiddler to track what is going on in the background.
Regards,
Lydia
Thanks, it turns out that there is a limit to the URL length as part of the API.
I do have a follow on question related to the conversion of a GET request, which can't handle the URL length, to a POST request which should be able to. That question is posted here. If you are able to have a look at this it would be much appreciated.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.