| HTTP Status Code 100 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| irwin williams New member Username: Irwin Post Number: 2 Registered: 02-2006 |
Hi, I'm implementing a VASP solution that talks to a nowsms mmsc. Part of my solution involves using iis as my web server. I have configured nowsms to post deliverreq messages to iis. Apparently during that interaction, prior to submitting my deliverrsp IIS, sends the listener of nowsms an HTTP 100 response. which the nowsms listener didnt seem to expect. I assume this because in the log file the mmsc states: "ThreadProcessVASPQ: mm7 - got unknown response ThreadProcessVASPQ: HTTP/1.1 100 Continue " However, if i use and application that does not send these intermediary status responses. the mmsc is fine. Is this something that nowsms should look at, or should i just avoid using servers like IIS. (I understand though, that HTTP says that a listening application receiving a status:100 response should be able to cope with that). Irwin | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6323 Registered: 10-2002 |
Hi Irwin, You don't mention what version of NowSMS you are using. I do know that some versions could not hanlde a VASP connection that returns an HTTP 100 response. But there should be no problems in the current release, NowSMS 2006. If you can provide me with your version information, I might be able to provide further guidance. -bn | |||
