title: Slack Slash Commands trigger GET request with no query parms
body: <p>I am trying to extend Slack by creating a Slack App that installs Slash Commands when the Slack App is installed by the user. The Slash Commands when triggered by a Slack chat user, will interact with an external web service that I am trying to develop.</p>
  
  <p>According to the Slack documents for Slash Commands (<a href="https://api.slack.com/slash-commands" rel="nofollow">https://api.slack.com/slash-commands</a>), any Slash command will trigger a POST to the external service with a set of parameters in the POST body to indicate among other things, the user, the Slack channel, etc., that triggered the request.</p>
  
  <p>When I made the web service I am developing on localhost available to the Internet using localtunnel (<a href="https://www.npmjs.com/package/localtunnel" rel="nofollow">https://www.npmjs.com/package/localtunnel</a>),  localtunnel actually creates a virtual server with some random hostname on <code>localtunnel.me</code>, e.g., <a href="https://wkbtfodclm.localtunnel.me" rel="nofollow">https://wkbtfodclm.localtunnel.me</a>, which connects to my localhost.</p>
  
  <p>If I key in the Slash Command on my Slack chat, Slack successfully sends a POST request to the <code>localtunnel.me</code> server, which gets piped to my localhost.</p>
  
  <p>However, after I deploy to Heroku, which has a domain, e.g., <a href="https://example.com" rel="nofollow">https://example.com</a>, I notice that the Slash Command sends a GET request with no parameters to the server on Heroku. Has anybody experience this before?</p>