Hey
Rose,
I did a bit of reading about server side events and it seems pretty straightforward (once id done some reading and reviewed the curl command youve specified anyway!)
The events handlers in ReadyAPI! do something different and i think youre letting the word "event" obfuscate the issue, so id just ignore those for now.
Just to ensure im clear in regards to your understanding, you have some SSE component (which equates to Server Side Events if googled) which you poke via curl, this initiates a connection allowing multiple (>=1) push messages to be returned from the endpoint and the Content-Type of these >=1 messages is set as 'text/event-stream' correct?
That seems quite straightforward (without knowing anything about that particular datatype). I don't know what the -N switch does (other than disabling stuff) but the -H switch appears to set the Accept header value.
You just need to setup your REST request as you would any other if converting a curl request to ReadyAPI!
Im guessing here but id setup a GET request using the following endpoint and URI (https://localhost:8080/request/listen) and ensure you add the 'Accept' header parameter (there doesnt appear to be any other REST parameters defined according to your post) with the value of 'text/event-stream' to the request.
You havent mentioned any authentication scheme in your post so you might need to tailor that, but your endpoint is local so the above is at least the startoff point to setup your requests in ReadyAPI! with a view toward automation. Still a bit concerned about the -N switch and what this is actually setting, but without knowing any further info about what youre testing, you should be able to start setting it up in ReadyAPI!
Hope the above helps,
Nice one,
Rich
