Forum: Ruby http.post dropping trailing '}'

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
8aaebef80b3102f06190b84ef0d04155?d=identicon&s=25 Wilson Chen (femeref)
on 2007-03-28 01:03
I am making a call through http.post in Ruby 1.8.5.

uri = ...
data = '{}'
headers = ...
http.post(uri, data, headers)

Everything seems to work except that the trailing '}' in data is not
getting posted, as determined by the network analyzer WireShark.  My
entire posted data is just '{'.  Is there some sort of sanitization or
choping that I am unaware of?

Thanks.
Ac0085dae0703db56ad7f8cb9e1798ba?d=identicon&s=25 Phillip Gawlowski (Guest)
on 2007-03-28 01:29
(Received via mailing list)
Wilson Chen wrote:
> choping that I am unaware of?
you could either try String#dump to automagically create escape
characters, or escape the {} yourself with a backslash.

I have no clue, though, if that is feasible in regard to the receiving
end.

--
Phillip "CynicalRyan" Gawlowski

Rule of Open-Source Programming #11:

When a developer says he will work on something, he or she means
"maybe".
753dcb78b3a3651127665da4bed3c782?d=identicon&s=25 Brian Candler (Guest)
on 2007-03-28 21:34
(Received via mailing list)
On Wed, Mar 28, 2007 at 08:04:00AM +0900, Wilson Chen wrote:
> choping that I am unaware of?
Attached is a test case which proves everything is working OK, for me
anyway:

$ ruby posttest.rb
Listening on port 38449
<< request >>
POST /foo/bar HTTP/1.1
Accept: */*
Content-Type: text/plain
Content-Length: 2
Host: 127.0.0.1:38449

<< end headers >>
"{}"
Response: #<Net::HTTPServerError 500 Go away readbody=true>

This is ruby 1.8.4 (2005-12-24) [i486-linux] under Ubuntu 6.06

So I think you're probably misinterpreting your wireshark output, in
which
case maybe you should post it. Better still, post tcpdump -s0 -X -n
output.

Regards,

Brian.
This topic is locked and can not be replied to.