Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1224807" data-attributes="member: 82144">Actually, I take that all back! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite10" alt=":oops:" title="Oops!&nbsp; &nbsp; :oops:" loading="lazy" data-shortname=":oops:" />Read section 1.3.3 (&quot;search response&quot;) of the UPnP v1.1 spec linked above.The messages appear to be responses to a search request (I can determine that from the ST header). The specification says that all 3 headers are optional for a search request response.I don't know what the consequences would be if you were to make those headers optional. You'd have to check the code for yourself. However I suspect that there would be problems with the following sequence:1. Device search.2. Device found; headers not present.3. Time passes.4. Device sends periodic NOTIFY with headers present (in this case they are required).=&gt; library detects and notifies device remove + reconnect, or maybe reboot??? You'll have to test and see what happens.</blockquote>

[QUOTE="mm1352000, post: 1224807, member: 82144"] Actually, I take that all back! :oops: Read section 1.3.3 ("search response") of the UPnP v1.1 spec linked above. The messages appear to be responses to a search request (I can determine that from the ST header). The specification says that all 3 headers are optional for a search request response. I don't know what the consequences would be if you were to make those headers optional. You'd have to check the code for yourself. However I suspect that there would be problems with the following sequence: 1. Device search. 2. Device found; headers not present. 3. Time passes. 4. Device sends periodic NOTIFY with headers present (in this case they are required). => library detects and notifies device remove + reconnect, or maybe reboot??? You'll have to test and see what happens. [/QUOTE]

Verification