-
Notifications
You must be signed in to change notification settings - Fork 769
Closed
Labels
Bot Servicesequired for internal Azure reporting. Do not delete. Do not change color.equired for internal Azure reporting. Do not delete. Do not change color.EnhancementNew feature or request to evolve an additional featureNew feature or request to evolve an additional featureP1Painful if we don't fix, won't block releasingPainful if we don't fix, won't block releasingT-Shirt: L2 - 5 Days2 - 5 Dayscustomer-replied-toRequired for internal reporting. Do not delete.Required for internal reporting. Do not delete.customer-reportedRequired for internal Azure reporting. Do not delete.Required for internal Azure reporting. Do not delete.
Description
We have implemented a custom channel that is dependent on the directLine messages via the websocket. When running with the Bot Emulator Framework locally, we do not receive these websocket messages as documented. Because of this, our local code behaves differently than the code when executed in the cloud.
Our enterprise policy does not allow using NGROK as the suggested workaround for this issue.
We request the addition of the local directLine websocket handling into the Bot Emulator Framework.
Metadata
Metadata
Assignees
Labels
Bot Servicesequired for internal Azure reporting. Do not delete. Do not change color.equired for internal Azure reporting. Do not delete. Do not change color.EnhancementNew feature or request to evolve an additional featureNew feature or request to evolve an additional featureP1Painful if we don't fix, won't block releasingPainful if we don't fix, won't block releasingT-Shirt: L2 - 5 Days2 - 5 Dayscustomer-replied-toRequired for internal reporting. Do not delete.Required for internal reporting. Do not delete.customer-reportedRequired for internal Azure reporting. Do not delete.Required for internal Azure reporting. Do not delete.