User-agent doesn't change

[rafaelgondim]

Setting up the user-agent in the request headers doesn't affect anything

[a85]

Unfortunately this is a restriction of the XMLHttpRequest specification - (http://www.w3.org/TR/XMLHttpRequest/#the-setrequestheader-method) which Postman uses. I am going to add a prompt in the interface that these headers can not be set in the next release. Postman is going to support a proxy server in the future through which you can bypass this restriction.

[a85]

You can change the User-Agent now using the Chrome settings. Go inside the web inspector and press the Settings icon in the bottom right. A user-agent setting will come up.

[a85]

Work around for this will be available in the next Postman version using a Twisted proxy. Will put up the details on the Postman wiki.

[thesmart]

Kind of a security flaw to go through a 3rd-party Twisted proxy...

[a85]

Hmm. It's a simple script and available here - https://github.com/a85/POSTMan-Chrome-Extension/blob/master/proxy/proxy_server.py. You should only keep this running while you are testing an API with Postman though.

[reggi]

@a85 Using chrome settings works really well.