From a4f6139e728b0201de5d552c80f8d90256806a62 Mon Sep 17 00:00:00 2001 From: Luiz Augusto von Dentz Date: Sun, 22 Jan 2012 23:07:33 +0200 Subject: [PATCH] gobex: fix automatically including SRM header in CONNECT responses MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit GOEP 2.0 test specification forbids the server to include SRM headers in CONNECT response: "3.16 TP/SRM/BI-03-C Process an OBEX CONNECT request (incorrectly) containing a SRM header: • Expected Outcome Pass Verdict: – On receiving the invalid SRM header in the OBEX_CONNECT request, the IUT responds with a SUCCESS without a SRM header. – OBEX/L2CAP channel is established. Fail Verdict: – On receiving the invalid SRM header in the OBEX_CONNECT request, the IUT does not respond with a SUCCESS and/or includes a SRM header in the response. – OBEX/L2CAP channel is not established or OBEX/RFCOMM channel is established." --- gobex/gobex.c | 1 + 1 file changed, 1 insertion(+) diff --git a/gobex/gobex.c b/gobex/gobex.c index 03da84f6f..0853a9b81 100644 --- a/gobex/gobex.c +++ b/gobex/gobex.c @@ -588,6 +588,7 @@ gboolean g_obex_send(GObex *obex, GObexPacket *pkt, GError **err) switch (obex->rx_last_op) { case G_OBEX_OP_CONNECT: prepare_connect_rsp(obex, pkt); + break; case G_OBEX_OP_GET: case G_OBEX_OP_PUT: prepare_srm_rsp(obex, pkt); -- 2.47.3