> -----Original Message----- > From: Dan Allen [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 18, 2004 12:14 PM > To: [EMAIL PROTECTED] > Subject: configuration violating J2EE spec? > > > Before I go paging through the J2EE spec to find a defense, I want to > see if someone out there can offer advice in the following matter. In > our application, the configuration of the servers is such that any URL > with a context of "/apps/" is captured by the webserver, the URL is > rewritten with this context stripped and the resulting URL is passed > internally to the J2EE application server. For all intents and > purposes, the app server assumes that the URL requested was without > the "/apps/" context and processes the servlet mapping as such. > However, when the taglibs generate URLs, the "/apps/" portion is not > prepended and therefore a followup request by the client will not be > processed by the app server. Is this in violation of the J2EE spec > for the webserver to alter the URLs in this way?
Web server (ie apache) or application server (ie tomcat). Application server shouldn't be stripping off the context, and yes that would be a violation. Web server stripping off context... well if you tell it. Our webserver doesn't strip off context at all, because we tell it not to. If yours is, then yes your violating J2EE, but I don't think it's necesarily the web servers fault. > > > client > (requests http://hostname/apps/modulename/) > webserver > (rewrites internally to http://hostname/modulename/) > app server > (generates http://hostname/modulename/somefile.jsp) > client > (requests http://hostname/modulename/somefile.jsp) > webserver > (throws 404 error) > > Dan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
