400 Bad Request in SIM300 GPRS module

Projects Programming
1

I've got a SIM300 GPRS Module . And I want to make an HTTP Request to a PHP file with my GPRS Module.
This is the code of my AT Commands :

{
if(firstTimeInLoop){
GPRS.write("AT+CGATT=1");
GPRS.write("\n\r");
GPRS.write("AT+CGDCONT=1,"IP","airtelgprs.com"");
GPRS.write("\n\r");
GPRS.write("AT+CDNSCFG="208.67.222.222","208.67.220.220"");
GPRS.write("\n\r");
GPRS.write("AT+CSTT="airtelgprs.com","",""");
GPRS.write("\n\r");
GPRS.write("AT+CIICR");
GPRS.write("\n\r");
GPRS.write("AT+CIFSR");
GPRS.write("\n\r");
GPRS.write("AT+CIPSTATUS");
GPRS.write("\n\r");
GPRS.write("AT+CIPHEAD=1");
GPRS.write("\n\r");
GPRS.write("AT+CDNSORIP=1");
GPRS.write("\n\r");
GPRS.write("AT+CIPSTART="TCP","www.nationalyouthparty.org","80"");
GPRS.write("\n\r");
GPRS.write("AT+CIPSEND");
GPRS.write("\n\r");
GPRS.write("GET /stick/mail.php HTTP/1.1");
GPRS.write("Host: www.nationalyouthparty.org");
GPRS.write("Connection: keep-alive");
GPRS.write("Accept: /");
GPRS.write("");
GPRS.write("Accept-Language: en-us");
GPRS.write(ctrlZ);
GPRS.write("\n\r");

firstTimeInLoop = 0;
}

But in return from the server I'm getting 400 Bad Request. How to make it working ?

2

But in return from the browser I'm getting 400 Bad Request. How to make it working ?

What does this mean? What browser? The code you posted is having the Arduino act as a client (the same role a browser fills).

A 400 return code usually means that the requested file does not exist. That is there is no /stick/mail.php at www.nationalyouthparty.org.

3

PaulS:

But in return from the browser I'm getting 400 Bad Request. How to make it working ?

What does this mean? What browser? The code you posted is having the Arduino act as a client (the same role a browser fills).

A 400 return code usually means that the requested file does not exist. That is there is no /stick/mail.php at www.nationalyouthparty.org.

Sorry . I edited my question. And the file do exist at the server . Because otherwise I would get 404 error and not 400.

4

Are you able to look at the logs on the server? They will show what the GET request looked like, and some other clues.