P
Peter Judge
Guest
You’re running into the same issue as community.progress.com/.../26828 . There is a bug in the HTTP client that has not been fixed yet. The root cause is that the boundary in the response’s Content-Type header has quotes and the HTTP client is not removing them appropriately so the body-parser thinks that the boundary is “----=_Part_8444890_801700095.1529449048289” Instead of ----=_Part_8444890_801700095.1529449048289 Unfortunately there are no simple workaround at the moment; code changes are required to the OpenEdge.Net.HTTP.ContentTypeHeader class.
Continue reading...
Continue reading...