Invalid host about openapi-parser HOT 4 CLOSED

Thank you for your feedback @juhakivekas.

I am very busy at thye moment, I will have to time to take a look at this issue only next week.

I saw your merge request, which I approuved.

Did it fix this issue?

from openapi-parser.

I can't verify at the moment because the code doesn't compile on my debian with up to date default-jre from apt repositories. I'll try to get the code to compile and I'll let you know as soon as I do. At the moment I'm still getting six errors, but I'll be working on this code about an hour every morning this week.

from openapi-parser.

In Burps extender the host and port for sendToRepeater are passed in separate variables. The host some.random.host:8080 is a valid host according to the swagger specification, but not as a host in the Burp extender. This is the reason for the exception, and it seems this is just a use-case that hasn't been taken into account.

Swurg already guesses the port number based on the schemes field in the swagger file. In order to enable connecting to APIs not on the schemes default ports, the host parameter should first be checked for a port number, and if one is found, then this should be used instead of the value returned by protocolToPort(protocol).

from openapi-parser.

A solution is now implemented, an update will soon follow.
My solution is to check if the schema field is empty, if it is the case rather than returning a null pointer, the plugin will now check the host for the presence of a port. If none of these conditions are met an exception will be raised.
Many thanks to @juhakivekas for reporting this issue and providing very usefull information.

from openapi-parser.