title: SMS Gateway for SMS Notifications with Worklight using HTTP POST?
body: <p>I'm using IBM Worklight Studio V6.2.0.0 and I would like to use Worklight SMS Notification messages with Skebby SMS Broker. I configured the <code>SMSConfig.xml</code> file as well for the Broker according to <a href="http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m5/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fadmin%2Fr_sms_gateway_config.html" rel="nofollow">Worklight documentation</a> and <a href="http://www.skebby.com/business/index/send-docs/#sendSMSClassicMethodSection" rel="nofollow" title="SMS Classic">Skebby documentation API</a> :</p>
  
  <pre><code>&lt;sms:config xmlns:sms="http://www.worklight.com/sms/config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&gt;
     &lt;gateway id="skebby" hostname="gateway.skebby.it" port="80" 
              programName="api/send/smseasy/advanced/http.php" toParamName="recipients[]" textParamName="text"&gt;
          &lt;parameter encode="true" name="method" value="send_sms_classic"/&gt;
          &lt;parameter encode="true" name="username" value="foo"/&gt;
          &lt;parameter encode="true" name="password" value="foo"/&gt;
          &lt;parameter encode="true" name="sender_string" value="Foo"/&gt; 
      &lt;/gateway&gt;
  &lt;/sms:config&gt;    
  </code></pre>
  
  <p>From WebSphere Console output, I don't see any error but analyzing HTTP traffic, I see an error since the request is made by HTTP GET and this method but only POST is allowed. </p>
  
  <p>How can I "force" HTTP POST instead of GET?</p>
  
  <p>Then I tried to use HTTPS using port 443 with no luck getting a ClientProtocolException, is it possible to use HTTPS?</p>
  
  <p>Then I've figured out that the value <code>recipients[]</code> of the <code>toParamName</code> key is urlencoded <code>recipients%5B%5D=</code>, how to avoid also this?</p>
  
  <p>Thanks</p>