api2swagger Fix error when response does not have a content-type header

Fix error when response does not have a content-type header

Open ctuckz opened this issue 7 years ago • 2 comments

Fixes #5 by checking for an undefined content-type header in the response before accessing it.

Sep 16 '17 20:09 ctuckz

can this be merged so that available to all who facing this issue ?

Apr 25 '19 02:04 nitingautam

I cloned this fix in local and tested worked fine :) thanks

Apr 25 '19 02:04 nitingautam