Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /www/htdocs/w006661d/anddev/includes/utf/utf_tools.php on line 1781[phpBB Debug] PHP Notice: in file /includes/session.php on line 1007: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)[phpBB Debug] PHP Notice: in file /includes/session.php on line 1007: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)[phpBB Debug] PHP Notice: in file /includes/session.php on line 1007: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)

Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /www/htdocs/w006661d/anddev/includes/utf/utf_tools.php on line 1781

Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /www/htdocs/w006661d/anddev/includes/utf/utf_tools.php on line 1781[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4362: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4364: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4365: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4366: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)anddev.org • View topic - 3G and Wifi

This is an odd one. Atleast for me it is. I wrote an app that opens a socket to see if a port is responsive on a specific host. This works great in the emulator and on wifi, but when I run it on 3g it always shows the port is up and running. I put out some debug statements, it is true, it is connected to the specific host / port. Any ideas why this would occur?

Does 3g require extra permissions? Is the tmo firewall doing some sort of nat on it? STRANGE!!!!

More than likely your 3G provider is running all traffic on its network through a proxy, and since they have no way to know for sure, the proxy is 'wide open' on all ports .. bad proxy! Its reporting open a port that isn't really open or serviced ..

I changed the code to print out a message, then wait for a reply. This works great for most of the ports but http (80), 80 always times out and there is nothing ever returned. Any ideas on how to trap http ports and keep them from timing out.