Lawrence D'Anna

@kdaily > Have you seen this behavior in the wild with an actual request? Yes, I encountered it when I was writing some unit tests for my application using s3mock.

um, sorry I didn't respond to that question @kdaily. No actual AWS endpoints don't generate responses like that one as far as I know.

thanks for responding! What you've got would work, but I think returning an error directly from `First()` and `Next()` would be more go-like and easier to use. What do you...

doesn't adding a new method to the interface also break the API?