Space was Not encoded to %20 | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 01, 2004 ⬆ |
◄ ► |
Author | Message | |||
Nambu New member Username: Nambu Post Number: 4 Registered: 08-2004 |
Hi all, My English is weak, sorry. I made simple HTTP program and received the output of NowSMS. # The setting of server type is NowSMS. I submit the text SMS "Test Message" using Web Interface, NowSMS outputted URI was set to "Test Message". Isn't it set to "Test%20Message" ? In another PC which the same setup, it is set to "Test%20Message". Why is an action different? | |||
Nambu New member Username: Nambu Post Number: 5 Registered: 08-2004 |
This is a supplement. I submit the text SMS "%20" using Web Interface, NowSMS outputted URI was set to "%20". '%' is not encoded into "%25". version : 5.51 build : 20040823 | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3615 Registered: 10-2002 |
Hi Nambu, I do not see the same behaviour. Are you sure that you are inputing the "%20" correctly. Here is what I see: 1.) If I use the web form of NowSMS ("Send Text Message"), and put Test%20Message in the "Text:" field, then if NowSMS is configured to submit the message to an HTTP SMSC, it gets submitted in the URL as "Test%2520Message". 2.) If I submit a URL to NowSMS with "Text=Test%20Message", and NowSMS is configured to submit the message to an HTTP SMSC, it gets submitted in the URL as "Test%20Message". Both of these behaviours are correct. So, you and I must have something configured differently. My advice would be to enable the SMSDEBUG.LOG (do this on the "Serial #" page). Restart the NowSMS service. Submit another message. In this log file, we can see the HTTP request from your message submission, as well as the HTTP request sent out by NowSMS. Please post this file if you need help about the URL requests or have any questions about what you see in those URLs. -bn | |||
Nambu New member Username: Nambu Post Number: 6 Registered: 08-2004 |
Thank you for a reply. I looked at SMSDEBUG.LOG, and I thought that a problem was in my program. Thank you for advising on SMSDEBUG.LOG. It was very useful. Thanks |