Re: [jetty-users] Parsing of URL

[Jan Bartel <janb@xxxxxxxxxxx>]

Martin,

/lgnrg is not the same as /lgnrg/whatever.

If you have configured the servlet to match the url-pattern /lgnrg,
only requests that exactly end in /lgnrg will match exactly (request
params are ok like ?x=y as these don't form part of the matching
algorithm). A trailing "/" announces another path segment. If you want
to match /lgnrg/whatever (where 'whatever' can be empty or arbitrarily
deep) then you need to use the url-pattern in the servlet declaration
of /lgnrg/*

You should see this if you do it at the command line with the 2
different urls you supplied in your email:
https://apply.satac.edu.au/lgnrg/x?loginCycle=unis2014 and
https://apply.satac.edu.au/lgnrg?loginCycle=unis2014

Jan

On 2 July 2014 01:07, Martin Edge <martin.edge@xxxxxxxxxxxx> wrote:
> The system is embedded and configured so that both URLs use the same servlet
> via the one configuration (IE  "/lgnrg" goes to
> RegistrationLoginServlet.class).
>
> I would have assumed that this would be irrelevant and both URLs would be
> the same, it is just a weird occurrence and after exhausting other avenues
> of investigation I’d thought I’d ask other users who might have come across
> this before.
>
> I am not surprised at all that it isn’t a jetty issue, but I am lost as to
> why this would occur. As it occurs only under load it might simply be the
> load testing itself.
>
>
>
> Anyway, thanks for the response,
>
>
>
> -medge
>
>
>
>
>
>
>
> From: jetty-users-bounces@xxxxxxxxxxx
> [mailto:jetty-users-bounces@xxxxxxxxxxx] On Behalf Of Joakim Erdfelt
> Sent: Wednesday, 2 July 2014 03:13
> To: JETTY user mailing list
> Subject: Re: [jetty-users] Parsing of URL
>
>
>
> Not enough information to go on.
>
> Its highly unlikely to be a URL parsing issue.
>
> As your two examples are about as simple as URLs can get.
>
> You'll probably want to profile your two requests and see what is using all
> of the resources/time, or what is waiting so long.
>
>
> --
>
> Joakim Erdfelt <joakim@xxxxxxxxxxx>
>
> webtide.com - intalio.com/jetty
>
> Expert advice, services and support from from the Jetty & CometD experts
>
> eclipse.org/jetty - cometd.org
>
>
>
> On Mon, Jun 30, 2014 at 9:07 PM, Martin Edge <martin.edge@xxxxxxxxxxxx>
> wrote:
>
> Currently have a Jetty 9.1.5 and have done a load test on the main server.
>
>
>
> It loaded one page (https://apply.satac.edu.au/lgnrg/x?loginCycle=unis2014)
> quickly, but another which uses exactly the same code
> (https://apply.satac.edu.au/lgnrg?loginCycle=unis2014) really slowly.
>
> The only thing I can think of is that there is a parsing issue. The work
> around is obvious(use the /), but is there an issue inside Jetty that would
> explain this or do I need to look further into it at my end?
>
>
>
> -medge
>
>
> _______________________________________________
> jetty-users mailing list
> jetty-users@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
>
>
>
> _______________________________________________
> jetty-users mailing list
> jetty-users@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/jetty-users



-- 
Jan Bartel <janb@xxxxxxxxxxx>
www.webtide.com
'Expert Jetty/CometD developer,production,operations advice'