Bilal Soylu

There are other high vulnerability issues flagged in 4.0.3. => run `npm audit` Understood that this may only manifest itself in development but would be nice to see attention as...

All verbs are supported. The connector does not override the verb. Can you check whether you use a URL rewriter ? Best, B

OK. I think I found your issue. PATCH is not one of the verbs supported by the AJP protocol. If we find a verb that is not supported we default...

@ajlemke That could be done as enhancement request. I am marking it as such. Given that the main AJP documentation is still not reflecting this exception implementation as indicated in...

Thanks for feedback. @bhartsfield the current workaround is to use another verb We are still looking for contributors that can help implement.

At first glance the setup looks ok. Is there something that prevents you from upgrading to latest version 1.0.41?

Thanks for the details. The connector should not introduce its own data in logs, it should only reflect what it sees in the protocol packets. The null in the log...

That is a good find. It looks like a HTTP 500 was thrown by tomcat during processing. `java.lang.ArrayIndexOutOfBoundsException: Requested read of bytes at position [6] which is beyond the end...

@joew7 we are still looking for some assistance to see whether we can make changes on the connector side to address this issue @uamaxua Thanks for publishing the work-around

@metadag This seem like odd behavior. Especially as it relates to packet size. Also IIS version should not impact BonCode in this manner. The only reason I can imagine is...