| HTTP Request Logs / Multiple Requests per single SMSIN |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 31, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Dave O'Keeffe New member Username: Daveokeeffe Post Number: 1 Registered: 08-2007 |
We've been having some strange problems on the server that hosts the script our NowSMS installation redirects all texts too, and I was hoping that NowSMS would log all outgoing Http Requests someplace. Our version is NowSMS v5.5.0 (can't remember build number right now). So, is this feature in v5.5? If not, is it in the later versions? The problem we're having is that it looks like NowSMS is sending multiple http requests triggered by single SMS's. I'm not saying that's what's happening, but it DOES look like it. Is there a feature where a 'HTTP/500 Internal Server Error' response would cause NowSMS to re-queue the request for a later time? Any help greatly appreciated, and congrats on a top class app. Even though we're on 5.5, we're still more than happy with it. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7461 Registered: 10-2002 |
Hi Dave, You're talking about the 2-way command processor, right? Back with older versions, it seemed like we had a lot of discussion threads with complaints about NowSMS' retry logic with regard to 2-way command processing. As I recall, if the 2-way command script returned an HTTP error response (like 500 - internal error), then NowSMS would retry the message. While this logic made sense to us, it caused problems for end-users when they encountered messages that contained particular characters that would cause their scripts to return errors. (As I recall, ASP doesn't like "<" or ">" characters in a URL variable unless you set a particular flag in your script.) Current versions of NowSMS retry a message to the 2-way command processor only if they encounter a communication-type error (e.g., web site not available). If the script returns an error, the message file remains in the SMS-IN directory with a ".BAD" file extension. So ... what can you do? If you are using ASP, here's the thread that talks about the character problem: http://support.nowsms.com/discus/messages/1/12418.html I also found some discussion here: http://support.nowsms.com/discus/messages/485/12885.html Based on that discussion, it looks like there wasn't a change to how NowSMS handled things until the NowSMS 2006 release. Back to the question about log files ... we don't log all of the HTTP requests. We do log the messages into the SMSIN-yyyymmdd.LOG file, but not the HTTP requests. -bn | |||
