You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! We have a backend that's processing batches of events. While I was doing some debugging locally, I noticed that if the delivery strategy is set to batching, specifying the protocol as 'http' doesn't have any effect, and the calls are still sent through HTTPS.
Once I disabled batching, specifying the protocol as 'http' started working.
Hello! We have a backend that's processing batches of events. While I was doing some debugging locally, I noticed that if the delivery strategy is set to batching, specifying the protocol as 'http' doesn't have any effect, and the calls are still sent through HTTPS.
Once I disabled batching, specifying the protocol as 'http' started working.
Is this by design or can something be done here to allow batches to go through http?
The text was updated successfully, but these errors were encountered: