Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
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.
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Join Fabric Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.
| User | Count |
|---|---|
| 8 | |
| 5 | |
| 5 | |
| 4 | |
| 4 |