Solved: Is there a maximum URL length for the Web.Contents...

Anonymous · ‎08-21-2018

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?

Anonymous · ‎08-22-2018

@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

View solution in original post

Anonymous · ‎08-22-2018

@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 · ‎08-22-2018

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.