<div class="im">[resending because numpty here forgot to reply-to-all. Sorry!]<br><br>On 9 August 2011 11:24, Steve Powell <span dir="ltr"><<a href="mailto:steve@rabbitmq.com" target="_blank">steve@rabbitmq.com</a>></span> wrote:<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Thanks for the confirmation that you included a content-length. Any ideas on the proper behaviour when it is omitted?</div></blockquote></div><div><br>Content-length
should only control the frame delimiting process, and shouldn't make
any difference to the interpretation of the content of a message.<br>
<br></div><div class="im"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex"><div style="word-wrap:break-word"><div>Indeed,
we would never want to add incorrect information to a message. In this
case, we clearly make the wrong default assumption.</div>
</div></blockquote></div><div><br>If the content-type is absent when the
broker receives a message, it should remain absent when the broker
processes and relays on that message. The broker should <i>never</i> synthesize a content-type header.<br>
<br></div><div class="im"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex"><div style="word-wrap:break-word"><div>Of
course, knowing what the defaults MUST be is surely better than only
knowing what they SHOULD be. Perhaps you can help to improve the
specification for us here.</div>
</div></blockquote></div><br>Perhaps in section "Header
content-type" the first paragraph could be augmented with the sentence
"A message broker or other relay MUST NOT attempt to guess a
content-type if one is not specified by the original sender of a
message."<br>
<br>I can see where the confusion arose: there's a sentence in that
section, "It SHOULD be set to a mime type which
describes the format of the body to help the receiver of the frame
interpret
it's contents", which chooses the word "set" poorly. That sentence
should probably be changed to read "When present, the content-type
header SHOULD be interpreted as being a mime type which
describes the format of the body to help the receiver of the frame
interpret
its contents", as well, thus avoiding the suggestion that a relay should
"set" the header on the SENDer's behalf.<br><br>Cheers,<br><font color="#888888"> Tony</font>