Forum Discussion
Error - POSTMAN REST Client - Google Chrome - "Found invalid content-type. The content-type must be application/json" - Header IS set
- Jun 17, 2016
FIXED! The issue seems to have been caused by the Postman-Token header confusing the F5 (you can see it using chrome tools network tab) . Somehow the F5 was treating the Postman-Token as the Content-Type header. Disable the Postman-Token header (Settings > General > Headers > "Send Postman Token header") and the request gets through.
You can see the purpose of the Postman-token header here https://www.getpostman.com/docs/settings
Enable chrome tools for postman http://blog.getpostman.com/2014/01/27/enabling-chrome-developer-tools-inside-postman/
FIXED! The issue seems to have been caused by the Postman-Token header confusing the F5 (you can see it using chrome tools network tab) . Somehow the F5 was treating the Postman-Token as the Content-Type header. Disable the Postman-Token header (Settings > General > Headers > "Send Postman Token header") and the request gets through.
You can see the purpose of the Postman-token header here https://www.getpostman.com/docs/settings
Enable chrome tools for postman http://blog.getpostman.com/2014/01/27/enabling-chrome-developer-tools-inside-postman/
- codydearkland_2Jun 18, 2016NimbostratusOh man! Awesome! Thanks for the answer! Working great now!
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com