Hi, On 02/06/10 05:01, osiris123d wrote: > > I still can't do a ngrep capture since ngrep can't decode SSL as far as I > know, but I can type out a bad HTTP GET request from SNOM and also a good > HTTP GET request from Firefox. I think you will notice where the difference > is and I am not sure if OpenXCAP is getting confused by the difference or if > SNOM's code is wrong when it comes to XCAP GETS. There has to be an answer > in here somewhere. >
I'm a bit confused about your email, see inline comments. > > GOOD Firefox GET request (rewritten from Wireshark capture) > ******************************************** > GET > https://xcap.ae.com:443/[email protected]/resource-lists/users/sip:[email protected]/index > HTTP/1.1\r\n > Expert Info (Chat/Sequence): GET > https://xcap.ae.com:443/[email protected]/resource-lists/users/sip:[email protected]/index > HTTP/1.1\r\n > Message: GET > https://xcap.ae.com:443/[email protected]/resource-lists/users/sip:[email protected]/index > HTTP/1.1\r\n > Severity level: Chat > Group: Sequence > Request Method: GET > Request URI: > https://xcap.ae.com:443/[email protected]/resource-lists/users/sip:[email protected]/index > Request Version: HTTP/1.1 > Host: xcap.ae.com:443\r\n > Content-Length: 0\r\n > Content length: 0 > Accept-Language: en\r\n > Connection: Keep-Alive\r\n > Keep-Alive: 5\r\n > User-Agent: Mozilla/4.0 (compatible; snom360-SIP 8.2.29 1.1.3-m)\r\n > \r\n If these are the good requests why is there a Snom useragent? > > > > > BAD SNOM GET request (rewritten from Wireshark capture) > ******************************************** > GET /[email protected]/resource-lists/users/sip:[email protected]/index > HTTP/1.1\r\n > Expert Info (Chat/Sequence): GET > /[email protected]/resource-lists/users/sip:[email protected]/index > HTTP/1.1\r\n > Message: GET > /[email protected]/resource-lists/users/sip:[email protected]/index > HTTP/1.1\r\n > Severity level: Chat > Group: Sequence > Request Method: GET > Request URI: > /[email protected]/resource-lists/users/sip:[email protected]/index > Request Version: HTTP/1.1 > Host: xcap.ae.com\r\n > User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) > Gecko/20100401 Firefox/3.6.3\r\n > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8\r\n > Accept-Language: en-us,en;q=0.5\r\n > Accept-Encoding: gzip,deflate\r\n > Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7\r\n > Keep-Alive: 115\r\n > Connection: keep-alive\r\n > Cookie: __utma=87383048.501874217.1266983378.1266983378.1266983378.1; > __utmz=87383048.1266983378.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none)\r\n > \r\n Hum, does the Snom not send the full URI? Is there an HTTP trace tool available in the Snom config web? It'd make debugging easier... :-S Regards, -- Saúl Ibarra Corretgé AG Projects _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
