Parent: f55ddf7376b24c37d7004b047968d521be4b9e0f
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Committer: Marcel Holtmann <marcel@holtmann.org>
Date: 2012-12-04 23:22:05
Tree: a4b2e48e76dfa48766f1ad3d4de54f34cd3912eb
gobex: fix automatically including SRM header in CONNECT responses 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."
Diffstat
| M | gobex/gobex.c | | | 1 | + |
1 files changed, 1 insertions(+), 0 deletions(-)