boyney123/mockit

Add the ability to set response headers per endpoint

nodesocket opened this issue · 7 comments

nodesocket commented

Add the ability to specify key => value response headers per endpoint.

boyney123 commented

Great idea @nodesocket , I will add it on the TODO list, and hopefully, get something out this week

boyney123 commented

This might be simular to #23 .

Maybe the UI can have some key value pairs that are captured and sent.

boyney123 commented

image

Started to implement it, just working on the small details and maybe some validation.

nodesocket commented

@boyney123 awesome. 👍 One edge case, what happens if I put a header key that is outputted by the server already? Example: Content-Type: text/plain.

mu99y commented

@boyney123 Awesome 👍

boyney123 commented

image

Been working abit on this feature, hopefully, get it live this week 👍

One edge case, what happens if I put a header key that is outputted by the server already? Example: Content-Type: text/plain.

I will test this and see what happens, Im guessing something will just get overridden, but il check it out!

boyney123 commented

I'm happy to share with you that this feature is now live with MockIt 1.1.0 🎉

Head over to https://mockit.netlify.com/blog/ to find out more details

https://mockit.netlify.com/docs/routes/route-features#response-headers

Thanks for the idea @nodesocket