site_archiver@lists.apple.com Delivered-To: macnetworkprog@lists.apple.com Thanks .... and ending with Any further hints are appreciated. Thanks Alex Am 27.07.2009 um 19:07 schrieb Jim Luther: On Jul 27, 2009, at 9:56 AM, Alexander von Below wrote: - Jim _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/macnetworkprog/below%40mac.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40lists.... Before I go into details: As my code works on the Mac, is it possible this is a bug in Phone OS? But back to the results: Luckily, the Simulator exhibits the same issues as the device. But I am way too unexperienced to read the output, especially as it is encrypted. Even a small body produces lots of data, starting with (in the successful case): 20:09:20.622996 IP 192.168.1.100.64711 > webdav.mediencenter.t- online.de.https: S 1101019046:1101019046(0) win 65535 <mss 1460,nop,wscale 3,nop,nop,timestamp 669833362 0,sackOK,eol> 20:09:23.776704 IP 192.168.1.100.64712 > webdav.mediencenter.t- online.de.https: R 2497493095:2497493095(0) win 0 E..( J@.@......d>..Y.......g....P....... Let me ask a stupid question: Can I read https data with tcpflow or Wireshark? Currently, I seem to be too unexperienced to do that You can see the data, but it'll be encrypted since you're seeing the data as it is on the wire. The standard port for https is 443 so make sure you add "port 443" to tcpflow/tcpdump's command line. This email sent to below@mac.com This email sent to site_archiver@lists.apple.com