View Single Post
Posts: 329 | Thanked: 505 times | Joined on Jul 2008 @ Israel
#318
Update status:
Just found the cause for the routing issue and it is a nasty nasty bug in Qt:
1) Using the recommended QNetworkAccessManager, I get status code 0 and remote disconnection error.
2) Using the deprecated QHttp, I get the response header OK (statuscode 200 && good content length), but in the finished slot I get a failure (statuscode = 6365312 with "Invalid HTTP response header").

EDIT: I have created QTBUG-26672 & currently Waze port is on halt until solution is found.

EDIT 2: QTBUG-26672 was closed as a server bug instead of being treated - Qt ppl failed to understand that I do not have any access to the Waze servers as I am just a whitehat hacker. The good news is that they had pointed me to exact problem with the server and so I have made the ugliest workaround yet! Now it is... well... kinda working but still needs some bugs fixing. Phew... that was a nasty bugger!

Last edited by damagedspline; 2012-07-28 at 08:13. Reason: QTBUG-26672 closed...
 

The Following User Says Thank You to damagedspline For This Useful Post: