Issue 38 in jayrock: JsonRpcClient Explicitly set Content-Length

2 views
Skip to first unread message

jay...@googlecode.com

unread,
Jun 30, 2011, 5:34:16 AM6/30/11
to jayrock...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium

New issue 38 by rgra...@gmail.com: JsonRpcClient Explicitly set
Content-Length
http://code.google.com/p/jayrock/issues/detail?id=38

What new or enhanced feature are you proposing?
Explicitly set the Content-Length before posting the request.

What goal would this enhancement help you achieve?
Some poorly implemented servers do not handle Expect: 100-continue http
header properly. The WebRequest automatically uses the Expect:
100-continue header when the application does not explicitly set the
Content-Length header before writing to the output stream. This is not a
bug in jayrock, but it is causing problems connecting to some servers.
Patch attached.

Attachments:
JsonRpcClient.cs 5.2 KB

jay...@googlecode.com

unread,
Aug 25, 2015, 5:23:45 AM8/25/15
to jayrock...@googlegroups.com

Comment #1 on issue 38 by azizatif: JsonRpcClient Explicitly set
Content-Length
https://code.google.com/p/jayrock/issues/detail?id=38

This issue has been migrated to:
https://github.com/atifaziz/Jayrock/issues/38
The conversation continues there.
DO NOT post any further comments to the issue tracker on Google Code as it
is shutting down.
You can also just subscribe to the issue on GitHub to receive notifications
of any further development.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Reply all
Reply to author
Forward
0 new messages