20, 2014 at 1:18 PM, Fiedler Roman
wrote:
> > Von: Tom Purcell [mailto:tpurc...@chariotsolutions.com]
> >
> > Roman
> >
> > I've used several clients (curl, a java application, postman) as well as
> the
> > mobile apps. All exhibit the same behavior: s
.
On Mon, Oct 20, 2014 at 3:57 AM, Fiedler Roman
wrote:
> Hello Tom,
>
> > Von: Tom Purcell [mailto:tpurc...@chariotsolutions.com]
> >
> > Hello
> >
> > We have an application that consists of REST endpoints on a jboss
> > server(5.1.0) fronted by
. We're running at warn. I can go to debug and see
what I see.
Thanks
Tom
On Fri, Oct 17, 2014 at 1:06 PM, Jeff Trawick wrote:
> On Fri, Oct 17, 2014 at 12:10 PM, Tom Purcell <
> tpurc...@chariotsolutions.com> wrote:
>
>> Hello
>>
>> We have an application that
ove does not mention the jboss server but
that the 400 does. I have verified that both requests hit the jboss server
by locating the stack traces in the jboss log.
- Normally there is an F5 in the mix and when hitting the app through it
we get the same results. That said the tests referred to here bypassed
the F5 and hit the Apache server directly
So we should get a 400 but when it gets to the client the response code is
200. Any thoughts?
--
Thanks,
Tom Purcell
Cell: 215-779-1963
