Transaction

d13c87bbd1bb8f144d676abfe2a4178747a942d0ff1a7c3b60f552b72e7bc421
Timestamp (utc)
2024-03-22 02:06:51
Fee Paid
0.00000013 BSV
(
0.00163612 BSV
-
0.00163599 BSV
)
Fee Rate
10.45 sat/KB
Version
1
Confirmations
93,893
Size Stats
1,244 B

2 Outputs

Total Output:
0.00163599 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMà<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=689.msg7299#msg7299">Quote from: gavinandresen on August 03, 2010, 06:56:44 PM</a></div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=689.msg7288#msg7288">Quote from: jgarzik on August 03, 2010, 06:09:08 PM</a></div><div class="quote">bitcoin requires the Content-Length header, but several JSON-RPC libraries do not provide it. &nbsp;When the Content-Length header is absent, bitcoin returns 500 Internal Server Error.<br/></div>Can you be more specific about which JSON libraries don't provide Content-Length ? &nbsp;It'd be nice to document that.<br/></div>I guess we should try to support the case where there's no Content-Length parameter. &nbsp;I don't want to rip and replace streams though, even if it has to read one character at a time.<br/><br/>Edit: That is, assuming there actually are any libraries that don't support Content-Length.</div> text/html
    https://whatsonchain.com/tx/d13c87bbd1bb8f144d676abfe2a4178747a942d0ff1a7c3b60f552b72e7bc421