HTTP headers are ASCII characters only (more accurately, ISO-8859-1 - slight differences from ASCII). So your protobuf message stored in the header may get bytes above the 127-character range of ASCII mangled. There's a few other issues here:
1. You're including the protobuf serialization in a header. Don't do this. Headers are for metadata, not data. The protobuf *is* your data, send that as the body. 2. The response you're using is HTML describing which message you processed, which you could/should do with a Content-Type header instead. My recommendation: use your own custom Content-Type subtype of octet-stream and use a parameter to state the name of the message type you decoded, like "application/vnd.some-fancy-name-specific-to-your-project+octet-stream; message-type=foo-message". Then send the serialized bytes as your response bytes, without any sort of wrapping in HTML at all. Also, remember to include a Content-Length header! -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
