Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Jetty 7.0.2 Invoker issue

I still have this issue and one other with the 7.0.2 code that I have not heard anything about.  Any chance someone can help me figure out if this is just me or if the Jetty code can be fixed?

Thanks
Tony

Tony Thompson wrote:
Some additional information...if I remove all of the filters from the context, the servlet works fine.  If I add even one filter back, it behaves the way I described below.

Tony

Tony Thompson wrote:
I am using the dynamic servlet Invoker (org.eclipse.jetty.servlet.Invoker) and I have issues with a non-mapped servlet.  The first time I request the servlet, Invoker finds and executes it.  The second and subsequent times I request the servlet, I get a 404.  I have tracked it down to this are in the Invoker code:

        String path_info = (String)request.getAttribute(Dispatcher.INCLUDE_PATH_INFO);  <--- This is always null for every request
        if (path_info==null)
            path_info=request.getPathInfo();  <--- on second and subsequent requests, this is null as well and obviously shouldn't be.
      
        // Get the servlet class
        String servlet = path_info;
        if (servlet==null || servlet.length()<=1 )
        {
            response.sendError(404);
            return;
        }



If I create a mapping for this servlet and use the mapping, it works every time.

Thoughts?

Thanks
Tony
 
This message (and any associated files) is intended only for the
use of the individual or entity to which it is addressed and may
contain information that is confidential, subject to copyright or
constitutes a trade secret. If you are not the intended recipient
you are hereby notified that any dissemination, copying or
distribution of this message, or files associated with this message,
is strictly prohibited. If you have received this message in error,
please notify us immediately by replying to the message and deleting
it from your computer. Messages sent to and from Stoneware, Inc.
may be monitored.


_______________________________________________ jetty-users mailing list jetty-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/jetty-users
 
This message (and any associated files) is intended only for the
use of the individual or entity to which it is addressed and may
contain information that is confidential, subject to copyright or
constitutes a trade secret. If you are not the intended recipient
you are hereby notified that any dissemination, copying or
distribution of this message, or files associated with this message,
is strictly prohibited. If you have received this message in error,
please notify us immediately by replying to the message and deleting
it from your computer. Messages sent to and from Stoneware, Inc.
may be monitored.


_______________________________________________ jetty-users mailing list jetty-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/jetty-users
 
This message (and any associated files) is intended only for the
use of the individual or entity to which it is addressed and may
contain information that is confidential, subject to copyright or
constitutes a trade secret. If you are not the intended recipient
you are hereby notified that any dissemination, copying or
distribution of this message, or files associated with this message,
is strictly prohibited. If you have received this message in error,
please notify us immediately by replying to the message and deleting
it from your computer. Messages sent to and from Stoneware, Inc.
may be monitored.


Back to the top