webdev, posts by tag: jsp - LiveJournal

Wow, this really seems retarded, but maybe I'm just utterly wrong.

Anyway.

If you have a jsp file a.jsp which includes b.jsp like so:
<jsp:include page="b.jsp />
or
<c:import url="b.jsp" />

And file b.jsp has some sort of logic that decides to redirect to another page, there's no way that redirect happens.

If I understand correctly, that's because b.jsp is completely processed by the server and is handed back to a.jsp as whatever static file results from that processing.

I'm trying to use this for authentication. As in, b.jsp checks whether or not the user is logged in, and if not, redirects to a login page. And this is obviously not working...

Any way to accomplish this?

I know I can do the authentication via JAAS or servlet filtering, but those two seem to complicated for the tiny website I'm building...

Very strange issue. I don't manage the server myself, but can request changes to its configuration.

The server is Apache Tomcat/5.5.9. We usually just write JSP files in Dreamweaver and upload them to the server.

Now here's the issue: Whenever we update a JSP file on the site and then go to view it in the browser, with equal probability we may see the old version of the file or the new one. If we make another change to the file, we may see any of the 3. This isn't a "local" caching issue because if I at the same time try this from another machine on another network, I get the same results.

We have attempted to delete the "cache" folder, but this doesn't generally help.

Any ideas?