Hi Vijitha/Chanika,
Adding that formatter and builders resolved the issue. Would this be the
correct fix or is this a workaround?
Chamila.
On Sun, Mar 4, 2018 at 11:35 AM, Vijitha Ekanayake
wrote:
> Hi Chamila,
>
> The reason that error doesn't print prior to the fix seems to
Hi Chamila,
The reason that error doesn't print prior to the fix seems to be that the
default content-type set as the application/x-www-form-urlencoded and
product distribution ships with the axis2.xml enabling the
relevant builder/formatter for that content-type. Could you try adding
following
Hi Vijitha,
Seems like the PR[1] is causing the issue. It sets content-type to
application/octet-stream for requests without a content-type header. Seems
like the logic is ok for POST request but not sure why that validation
related method is called for all other HTTP methods in [2].
[1]
++Chanika
On Fri, Mar 2, 2018 at 6:30 PM, Nuwan Dias wrote:
> Is there a release of EI happening in Q1? Don't you notice this error on
> latest versions of EI?
>
> On Fri, Feb 23, 2018 at 3:46 PM, Vijitha Ekanayake
> wrote:
>
>> This error is generated
Is there a release of EI happening in Q1? Don't you notice this error on
latest versions of EI?
On Fri, Feb 23, 2018 at 3:46 PM, Vijitha Ekanayake
wrote:
> This error is generated within the handleRESTUrlPost(...) method in
> ServerWorker class. So I think we need to
This error is generated within the handleRESTUrlPost(...) method in
ServerWorker class. So I think we need to investigate the reason why these
GET requests are landed in that method and fix if there is an issue in the
logic.
Thanks.
On Fri, Feb 23, 2018 at 3:20 PM, Chaminda Jayawardena
True, But I am trying with Jmeter and just tried since suggested above and
error is not appeared when it sends with Content-Type :)
Yes, have to fix it.
Thanks,
Chaminda
On Fri, Feb 23, 2018 at 3:12 PM, Nuwan Dias wrote:
> Well, for GET requests you aren't supposed to have a
Well, for GET requests you aren't supposed to have a Content-Type header.
On Fri, Feb 23, 2018 at 3:11 PM, Chaminda Jayawardena
wrote:
> Getting this continuously even for the GET requests in
> wso2apim-2.1.0-update12. Disappeared once put Content-Type(value as any
> format)
Getting this continuously even for the GET requests in
wso2apim-2.1.0-update12. Disappeared once put Content-Type(value as any
format) on the header.
Thanks,
Chaminda
On Fri, Feb 23, 2018 at 1:38 PM, Nuwan Dias wrote:
> I'm just doing a GET. I also checked with a POST with the
I'm just doing a GET. I also checked with a POST with the correct
Content-Type header as well.
On Fri, Feb 23, 2018 at 1:17 PM, Vijitha Ekanayake
wrote:
> Hi Nuwan,
>
> According to below code segment, it seems like this happens when request
> Content-Type doesn't match with
Hi Nuwan,
According to below code segment, it seems like this happens when request
Content-Type doesn't match with the payload.
try {
soapEnvelope = TransportUtils.createSOAPMessage(msgContext, null,
contentType);
} catch (Exception e) {
log.error("Error while building message for
11 matches
Mail list logo