Quick Tip #014: A Quick Note on Upgrading to 6.3.0.x When Using HTTP ReceiveSeveral of our customers have experienced issues related to migrating existing orchestrations that begin with an HTTP Receive Activity to version 6.3.0.x. (We've seen this issue in both 184.108.40.206 and 220.127.116.11, we have not tested 18.104.22.168 yet) I believe that the issues mostly come up when you are trying to manually parse the URI and simple use cases that don't do anything with the URI seem to work just fine. Our recommendation is that if you are using the HTTP Receive Activity as a starter for any of your orchestrations that you thoroughly regression test your orchestration. Additionally, if you are manually parsing the URI we recommend rebuilding the Activity to use the built in parsing functionality. See this post for more details on the new features of the HTTP Receive Activity. There are two main problems that we have encountered so far:
- Certain URI strings cause the Activity to throw an exception and prevent the job from starting. This is a bug that we discovered at a client today, if you have a query string in your URL with a parameter but no value, this will cause the HTTP Receive Activity to throw and exception. If you encounter this issue, the work around is to make sure that you pass a value to all your query parameters.
- this throws an exception: http://www.example.com/MyTestOrchestration?value
- this does not throw an exception: http://www.example.com/MyTestOrchestration?parameter=value