Any way to not reply to received messages?

[Solitude]

When I send a message to the number with my prefix, it always replies,
either with the callback stuff I've setup, or an error (when I dont
have my callback url send anything back). Is there a way to just not
respond?

Example:
User sends text to number + prefix.
Data sent to my callback page
Data processed.

And that's it. At the moment what it does is:

User sends text to number + prefix.
Data sent to my callback page
Data processed.
Response sent back to Zeep
Zeep texts the user back either w/ the response or an error

I don't want that last step. Possible?

Hopefully this wasn't confusing, I don't know the vocab too well.

[Simon Wex]

If you reply with an empty body, nothing should be sent to the user.
The only catch is that you must still set the content-type header to
'text/plain'.

Try that and let the group know if it doesn't work.

Cheers, Simon.

[Solitude]

Oh wow! I tried this before, but instead of leaving it empty, I just
didn't reply anything...

But yeah, an empty body and content-type set as 'text/plain' works
perfectly!

Thanks so much!

On Jun 24, 12:58 pm, Simon Wex <si...@simonwex.com> wrote:
> If you reply with an empty body, nothing should be sent to the user.
> The only catch is that you must still set the content-type header to
> 'text/plain'.
>
> Try that and let the group know if it doesn't work.
>
> Cheers, Simon.
>

[Solitude]

Wait so I was wrong! Just a few moments after sending, I got a
"communication error, please try again later". I think I must be doing
something wrong?

My callback URL is a php script. I've set the header correctly, and
then I do:

die(' my return message');

accordingly, (maybe this is the wrong function to use?), so instead I
did die('');

It still did everythin it was supposed to, just replied with the
error, instead of nothing.

Anyone use PHP for their callback URL and know what to do?

Thanks,
Payam

On Jun 24, 12:58 pm, Simon Wex <si...@simonwex.com> wrote:

> If you reply with an empty body, nothing should be sent to the user.
> The only catch is that you must still set the content-type header to
> 'text/plain'.
>
> Try that and let the group know if it doesn't work.
>
> Cheers, Simon.
>

[Simon Wex]

You will still need to reply with a status code of 200 OK. Otherwise
the zeep system will think you've had an error.

-Simon

[Solitude]

Okay, so you do that with headers right?

header("Status: 200");

like that?

On Jun 24, 2:12 pm, Simon Wex <si...@simonwex.com> wrote:
> You will still need to reply with a status code of 200 OK. Otherwise
> the zeep system will think you've had an error.
>
> -Simon
>

[Solitude]

Or should I use header('Status: HTTP/1.1 200 OK');

On Jun 24, 2:12 pm, Simon Wex <si...@simonwex.com> wrote:
> You will still need to reply with a status code of 200 OK. Otherwise
> the zeep system will think you've had an error.
>
> -Simon
>

[Solitude]

So I tried header('Status: HTTP/1.1 200 OK'), and header('HTTP/1.1 200
OK');
Neither work?

And I'm testing this on a test phone, could that be an issue?

[Adam Berger]

I've tested on a real phone and have the same problem. Is this a
bug? Anybody know of a fix?

[Hunter Fuller]

I don't think this is the issue, because your web server should reply
with the 200 already. Perhaps you don't want to die() - you should
send the header('Content-type: text/plain') and then just exit(). This
is a stab in the dark, though.

-- Hunter Fuller
Too short? http://five.sentenc.es/



2009/6/24 Solitude <solitu...@gmail.com>:

[scott...@yahoo.com]

Hi Simon,
I am having the same issue...

do you have any example code of this api call working? I am setting
the content-type to text/plain and not returning any text. Using IIS
as the web server, which automatically sets the status code to 200.

> > Hopefully this wasn't confusing, I don't know the vocab too well.- Hide quoted text -
>
> - Show quoted text -