httpGET always connects to port 80

MarcoMartines / GSM-GPRS-GPS-Shield

GSM/GPRS & GPS Shield Library for modules using SIM900/SIM908

GNU General Public License v2.0

208 stars 152 forks source link

httpGET always connects to port 80 #4

Closed madmaze closed 10 years ago

madmaze commented 10 years ago

Expected Behavior:

inet.attachGPRS()
inet.httpGET("", 8080, "/", txtbuffer, bufsize);
connect to on port 8080 and stick result in txtbuffer

Actual Behavior

inet.attachGPRS()
inet.httpGET("", 8080, "/", txtbuffer, bufsize);
Actually connects to on port 80 and sticks result in txtbuffer

I have looked through the code a bit, it looks like it writes the right things to module, but still it connects to port 80 and not 8080..

Need to double check how the connection is setup, reference here, around page 12: http://www.ele.tut.fi/teaching/ele-2000/sim900_tcpip.pdf

madmaze commented 10 years ago

actually, this looks like an issue related to T-mobile's proxying of connections.. anything that tries to connect on port 8080 actually connects on port 80..

Interestingly when nothing is available on port 80 t-mobile throws an HTTP 502 Bad Request though if it is a different port, not 80 or 8080, it doesn't care.

MarcoMartines commented 10 years ago

Great! If we think it is a module related problem, I can forward this issue to the SIMCom. Have you received the materials yet? Let me know. Marco Il 06/feb/2014 04:33 "Matthias Lee" notifications@github.com ha scritto:

actually, this looks like an issue related to T-mobile's proxying of connections.. anything that tries to connect on port 8080 actually connects on port 80..

Interestingly when nothing is available on port 80 t-mobile throws an HTTP 502 Bad Request though if it is a different port, not 80 or 8080, it doesn't care.

Reply to this email directly or view it on GitHubhttps://github.com/MarcoMartines/GSM-GPRS-GPS-Shield/issues/4#issuecomment-34289067 .