I'm a software developer working on backend services, always juggling between Firefox and Chrome (because none of them fully satisfy my needs). What I need from them is t… (διαβάστε περισσότερα)
I'm a software developer working on backend services, always juggling between Firefox and Chrome (because none of them fully satisfy my needs). What I need from them is to behave the way it will be most practical for me, which isn't necessarily aligned with the majority of users.
My current problem is this. I work with APIs which in my daily work often return various HTTP errors. These errors also contain a payload which describes the problem in detail. I want to be able to see this payload easily in the browser. Yes, I can use other tools like Postman for this (which I do), but for simple GET requests without special request headers it would be much more practical to just use a browser.
Currently, when my API opens an error (for example a 400 Bad Request), Firefox decides to just silently go back into the previous page (undos the URL change). If I open the Network tab in the Web Developer view, I can however see the failing response with all of its details. Still, this is too impractical for me.
BTW, the response contains a custom Content-Type which isn't recognized by Firefox by default. But Firefox isn't downloading the payload as a file (like it would usually do for a successful page load of an unknown Content-Type), it just silently doesn't do anything. I've installed an extension to handle my custom Content-Types (called "Open in Browser"), but since Firefox isn't attempting to open this one, I can't use it in this case.
So, how can I force Firefox to stay on that URL and show the response payload in the window? If not in vanilla Firefox, any plugins? I've already kind of spent too much time on this for my liking. :/