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
Currently, if HTTP/1.1 is used with a cowboy connection that has been configured with connection_type == worker, the first request will succeed with the connection and a second request performed immediately will fail. If that should not occur, it appears like source code would need to change, so currently connection_type must always be supervisor, right? Is there a way to use connection_type == worker now that isn't documented?
The text was updated successfully, but these errors were encountered:
It's only been tested with supervisor connection type. To allow setting it to worker we would need to disable spawning of processes, and supposedly fix the error you got. A stacktrace or other would be helpful.
Currently, if HTTP/1.1 is used with a cowboy connection that has been configured with
connection_type == worker
, the first request will succeed with the connection and a second request performed immediately will fail. If that should not occur, it appears like source code would need to change, so currentlyconnection_type
must always besupervisor
, right? Is there a way to useconnection_type == worker
now that isn't documented?The text was updated successfully, but these errors were encountered: