Bugzilla

Thanks!

> Sorry, I don't understand this. Can you explain more?
I think you answered my question with this: 
> Note that neqo doesn't write data to socket, it only prepare the data for you.

With this being the case, I was thinking  maybe we can set `:status 404` along with the error `HttpRequestRejected`. So the original test can stay and we can write an additional cargo test to explicitly test the error. But I will have a closer look. It's possible the header doesn't get sent in the circumstance we Error. If that's the case we will need to do as you suggest and modify the logic slightly.

Thanks!

> Sorry, I don't understand this. Can you explain more?

I think you answered my question with this: 
> Note that neqo doesn't write data to socket, it only prepare the data for you.

With this being the case, I was thinking  maybe we can set `:status 404` along with the error `HttpRequestRejected`. So the original test can stay and we can write an additional cargo test to explicitly test the error. But I will have a closer look. It's possible the header doesn't get sent in the circumstance we Error. If that's the case we will need to do as you suggest and modify the logic slightly.

Thanks!

> Sorry, I don't understand this. Can you explain more?

I think you answered my question with this: 
> Note that neqo doesn't write data to socket, it only prepare the data for you.

With this being the case, I was thinking  maybe we can set `:status 404` along with the error `HttpRequestRejected`. So the original test can stay and we can write an additional cargo test to explicitly test the error. But I will have a closer look. It's possible the header doesn't get sent in the circumstance we Error. If that's the case we will need to do as you suggest and modify the logic slightly to do one or the other.