Forum Discussion

alexgsl's avatar
13 years ago

Incorrect Content-Type in HTTP Monitor

When sniffing traffic using HTTP Monitor it displays incorrect Content-Type. Test step created from such request also contains wrong content type.

Problem occurs with POST requests having Content-Type="application/x-www-form-urlencoded".
HTTP Monitor displays "text/html; charset=utf-8" instead.

Steps to reproduce:
* Launch HTTP Monitor in SoapUI, start in proxy mode with default settings
* Configure web browser to use the proxy
* Open any page that generates POST, "application/x-www-form-urlencoded" request
* Open "developer tools" in your browser (Opera/Dragonfly, Firefox/Firebug, etc.)
* Submit request
* Using dev-tools ensure that request sent has "application/x-www-form-urlencoded" content type

Actual results:
* Inspect SoapUI's HTTP Monitor window: it contains "text/html; charset=utf-8" content type for appropriate request
* Try to create test step using captured request: Media Type also contains "text/html; charset=utf-8"

Expected results:
* "application/x-www-form-urlencoded" should be captured
No RepliesBe the first to reply