These headers were causing the connectivity test to fail when reporting status
to the website. With the usbnet headers in place, the website keeps trying to
force the user to upgrade their firmware. The connectivity test works fine
without the usbnet headers.
Signed-off-by: Scott Talbert <s...@techie.net>
---
libconcord/web.cpp | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/libconcord/web.cpp b/libconcord/web.cpp
index 6c00d7d..3b581e3 100644
--- a/libconcord/web.cpp
+++ b/libconcord/web.cpp
@@ -357,11 +357,7 @@ int Post(uint8_t *xml, uint32_t xml_size, const char
*root, TRemoteInfo &ri,
ri.fw_type, serial, ri.hw_ver_major, ri.hw_ver_minor,
ri.hw_ver_micro, ri.flash_mfg, ri.flash_id, ri.protocol,
ri.architecture, ri.skin);
- if (is_usbnet_remote()) {
- add_usbnet_headers(post_data, ri);
- } else {
- sprintf(post_data+strlen(post_data), "%s", post_xml_trailer);
- }
+ sprintf(post_data+strlen(post_data), "%s", post_xml_trailer);
}
debug("post data: %s",post_data);
--
1.8.1.4
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel
