解决自定义字体产生临时文件消耗硬盘的问题,以及解决总分操作系统下无法读到字体文件的问题
This commit is contained in:
@@ -0,0 +1,5 @@
|
||||
Manifest-Version: 1.0
|
||||
Created-By: IntelliJ IDEA
|
||||
Built-By: zrh
|
||||
Build-Jdk: 1.8.0_251
|
||||
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
15
classes/artifacts/EasyCaptcha_Web_exploded/WEB-INF/web.xml
Normal file
15
classes/artifacts/EasyCaptcha_Web_exploded/WEB-INF/web.xml
Normal file
@@ -0,0 +1,15 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee"
|
||||
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
|
||||
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_4_0.xsd"
|
||||
version="4.0">
|
||||
<!-- 图形验证码servlet -->
|
||||
<servlet>
|
||||
<servlet-name>CaptchaServlet</servlet-name>
|
||||
<servlet-class>com.wf.captcha.servlet.CaptchaServlet</servlet-class>
|
||||
</servlet>
|
||||
<servlet-mapping>
|
||||
<servlet-name>CaptchaServlet</servlet-name>
|
||||
<url-pattern>/captcha</url-pattern>
|
||||
</servlet-mapping>
|
||||
</web-app>
|
||||
10
classes/artifacts/EasyCaptcha_Web_exploded/index.html
Normal file
10
classes/artifacts/EasyCaptcha_Web_exploded/index.html
Normal file
@@ -0,0 +1,10 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<title>验证码测试</title>
|
||||
</head>
|
||||
<body>
|
||||
<img src="/captcha" width="130px" height="48px" />
|
||||
</body>
|
||||
</html>
|
||||
Reference in New Issue
Block a user