[Java Servlet] The road of Senri is also the fourth step from the first step
Progress
Finally last time
login.jsp → LoginServlet.java → mypage.jsp
You can now make transitions.
By the way, the URL at the time of mypage transition is
http://localhost:8080/ServletApp/mypage.jsp
However, if you are concerned about the last extension, go to web.xml
web.xml
<servlet>
<servlet-name>mypage</servlet-name>
<jsp-file>/mypage.jsp</jsp-file>
</servlet>
<servlet-mapping>
<servlet-name>mypage</servlet-name>
<url-pattern>/ServletApp/mypage</url-pattern>
</servlet-mapping>
If you add, the URL at the time of transition will be
http://localhost:8080/ServletApp/mypage
Will be.
Other data transfer methods
Actually, there are other methods called "cookies" and "sessions" for passing data between Servlets, in addition to the method using the request.getParameter () method that was done last time.
Let's make cookies
A cookie is information stored on the client side when a response is returned from the server. (If you often browse the site, you may see pop-ups such as "This site uses cookies".)
As a merit of saving data on the client side,
--Membership site → Omit user name input from next time --Shopping site → Remember the items you have added to your cart
And so on.
Let's make cookies. First, modify the doPost () method of LoginServlet.java.
LoginServlet.java
protected void doPost(HttpServletRequest req, HttpServletResponse res)
throws ServletException, IOException {
req.setCharacterEncoding("UTF-8");
String name=req.getParameter("name");
Cookie c[]=req.getCookies();
boolean CreatedCookie=false;
for(Cookie cookie:c) {
if(cookie.getName().equals("cookie_user")) {
CreatedCookie=true;
}
}
if(CreatedCookie==false) {
Cookie cookie=new Cookie("cookie_user",name);
res.addCookie(cookie);
}
// if(Arrays.stream(c)
// .filter(e->!e.getName().equals("cookie_user"))
// .count()==c.length) {
// Cookie cookie=new Cookie("cookie_user",name);
// res.addCookie(cookie);
// }
req.setAttribute("name",name);
req.getRequestDispatcher("/mypage.jsp").forward(req,res);
}
- The 6th to 15th lines and the comment-out line have almost the same movement except for the writing method. Please use it according to your preference.
--req.getCookies () ・ ・ ・ Get the cookies that the client has in an array (5th line)
--cookie.getName () ・ ・ ・ Get the name of the cookie (8th line)
--new Cookie (String name, String value) ・ ・ ・ Create a cookie with a pair of name: value (line 13) --res.addCookie (Cookie cookie)` ・ ・ ・ Set cookie as response (line 14)
This allows you to save the username you entered at login as cookie_user.
Also, although it does not appear here,
--cookie.setMaxAge (int seconds) ・ ・ ・ Specify the expiration date of the cookie in seconds (when the expiration date expires, the cookie will be destroyed)
--cookie.setValue (String value) ・ ・ ・ Reset the value to the cookie
And so on.
Next, modify the inside of the <body> tag of login.jsp.
login.jsp
<body>
<%
Cookie cookies[]=request.getCookies();
String username="";
for(Cookie c:cookies){
if(c.getName().equals("cookie_user"))username=c.getValue();
}
%>
<form action="/ServletApp/mypage" method="post">
name:<input type="text" name="name" value=<%=username%>><br>
password:<input type="text" name="password"><br>
<input type="submit" value="login">
</form>
</body>
If the cookie name cookie_user already exists when the login screen is displayed, the value will be entered in the text field.
Let's use cookies
Now access login.jsp.
Enter "hato" in name to log in.
At first glance it looks like nothing has changed, but let's access login.jsp again.
You can see that the "hato" that was already entered is already entered in name.
Let's check cookies
I said "information stored on the client side" in [Let's make cookies](# Let's make cookies), but there is a way to check the cookies stored in Google Chrome.
-
With
login.jspopen, press theF12key to open "Developer Tools". -
Click the ʻApplication` tab in the menu.
-
Click
Cookies.
-
Click
http: // localhost: 8080.
accomplished.
In Name,cookie_user, which is the name of the cookie created earlier, is displayed, and "Hato", which is the user name entered inValue, is displayed. You can also rewrite or delete the value on this screen.
Let's make a session
A session refers to a series of processes from the start to the end (or discard) of a connection, such as "from login to logout" or "after login to leaving it to time out".
However, since a normal Web page does not have a function to pass the "connected state", it will be treated as a different connection every time you access the server as shown below.
Let's make this connection A to C a series of processes (sessions).
Add the following code to LoginServlet.java.
LoginServlet.java
HttpSession session=req.getSession();
Date date=new Date(session.getCreationTime());
SimpleDateFormat sdf=new SimpleDateFormat("yyyy/MM/dd HH:mm:ss");
session.setAttribute("lastLoginDate", sdf.format(date));
session.setMaxInactiveInterval(20);
Code that saves the session start time with the name lastLoginDate.
--req.getSession () ・ ・ ・ Get session
--session.getCreationTime () ・ ・ ・ Get the date and time when the session was first created as a long type
--session.setAttribute (String name, Object value) ・ ・ ・ Name: Value pair stores parameters
--session.setMaxInactiveInterval (int s) ・ ・ ・ Specify the session expiration date with seconds (default should be 1800 seconds)
Also modify mypage.jsp.
mypage.jsp
<body>
<%
String name=request.getParameter("name");
String session_date=session.getAttribute("lastLoginDate").toString();
%>
<%=name%>Login date and time<%=session_date%>is.
</body>
--session.getAttribute (String name) ・ ・ ・ Get the value corresponding to the name specified by the argument from within the session with ʻObject type`
Also, I will not use it this time
--session.getAttributeNames () ・ ・ ・ Get the parameter names stored in the session as a String type array`` --session.lastAccessedTime ()` ・ ・ ・ Get the last connected time in the session
And so on.
Let's use the session
Now access login.jsp again.
Enter "Hato" to log in.
I think that the current time is roughly displayed.
Then, refresh the page with the F5 key without a break (do not do it on the real input form or product page)
The time does not change. The 20 seconds you set the expiration date earlier are considered "same connection".
Then reload after a while.
Since a session is also a type of cookie, you can check the session in the same way as [Let's check cookies](#Let's check cookies). However, it is a difficult character string so that it cannot be modified as much as possible.
That's all for this time. I wonder if I can put it in the framework soon ...
Recommended Posts