


javascript - What is the reason for this? [Network security, nginx, php, js related]
Solved, replaced jquery import with Qiniu Cloud static resource acceleration. Then this problem no longer occurs.
It means there is a problem inside the js file. I also reminded myself not to use external js indiscriminately. Thank you to those who answered!
After occasionally refreshing the page, normally it should all come from the same address. Why are there three things requested from external addresses? (The black lines above are all from the same address, and the yellow lines are from other addresses)
Normal should be like this:
I am a front-end person, I don’t quite understand why this is? (Guess whether the router or server was hijacked?)
1. CDN is not used.
2.js references only jquery and layui.
3. It is just a login page and does not use js from external resources.
4.This is the page header:
Reply content:
Solved, replaced jquery import with Qiniu Cloud static resource acceleration. Then this problem no longer occurs.
It means there is a problem inside the js file. I also reminded myself not to use external js indiscriminately. Thank you to those who answered!
After occasionally refreshing the page, normally it should all come from the same address. Why are there three things requested from external addresses? (The black lines above are all from the same address, and the yellow lines are from other addresses)
Normal should be like this:
I am a front-end person, I don’t quite understand why this is? (Guess whether the router or server was hijacked?)
1. No cdn is used.
2.js references only jquery and layui.
3. It is just a login page and does not use js from external resources.
4.This is the page header:
Excuse me, the poster, is your IP address the IP address in the yellow part above? Looking at these three resource types, two are script
and one is img
. I'm a bit doubtful whether it's something that was initialized by the js plug-in you quoted? (Another one, you coded the domain name, but the domain names linked to the questions were not coded, snickering.jpg)
Laxative~
There is no code, I can’t tell anything just by looking at the pictures~
There are many sources of external resources, you can check them out:
Browser extensions, some extensions will reference additional external resources for the page
CSS, CSS files can also load other external css, images, and fonts
HTML, images and the like can also be loaded and generated from external resources. (But it doesn’t look like you, if the html is written by yourself)
JS, it may also be loading external resources. You need to make sure whether it is downloaded from the official website.
The resources referenced may include third-party resources. Check whether the css uses other images and whether the js sends other requests.
Ping your website to see if it is the IP address. It may be a configuration issue with the domain name operator.
Tell me a few possibilities and let the questioner debug it himself.
1. Check the installed browser plug-ins. Some plug-ins will request data from the server and other corresponding logic.
2. Check whether it is a statistics script.
3. Check whether it is the operator's advertising script.
4. Check whether it is xssed. After all, you can see that the request brings the path of the current page, and it is also the management path. Focus on what the two script requests are!
5. Check whether external resources are imported in the css resources.
6. Check the referenced js plugin.
I saw that there are also image resources, which look like statistics or advertisements. It is more likely that they have been xssed.

Reasons for PHPSession failure include configuration errors, cookie issues, and session expiration. 1. Configuration error: Check and set the correct session.save_path. 2.Cookie problem: Make sure the cookie is set correctly. 3.Session expires: Adjust session.gc_maxlifetime value to extend session time.

Methods to debug session problems in PHP include: 1. Check whether the session is started correctly; 2. Verify the delivery of the session ID; 3. Check the storage and reading of session data; 4. Check the server configuration. By outputting session ID and data, viewing session file content, etc., you can effectively diagnose and solve session-related problems.

Multiple calls to session_start() will result in warning messages and possible data overwrites. 1) PHP will issue a warning, prompting that the session has been started. 2) It may cause unexpected overwriting of session data. 3) Use session_status() to check the session status to avoid repeated calls.

Configuring the session lifecycle in PHP can be achieved by setting session.gc_maxlifetime and session.cookie_lifetime. 1) session.gc_maxlifetime controls the survival time of server-side session data, 2) session.cookie_lifetime controls the life cycle of client cookies. When set to 0, the cookie expires when the browser is closed.

The main advantages of using database storage sessions include persistence, scalability, and security. 1. Persistence: Even if the server restarts, the session data can remain unchanged. 2. Scalability: Applicable to distributed systems, ensuring that session data is synchronized between multiple servers. 3. Security: The database provides encrypted storage to protect sensitive information.

Implementing custom session processing in PHP can be done by implementing the SessionHandlerInterface interface. The specific steps include: 1) Creating a class that implements SessionHandlerInterface, such as CustomSessionHandler; 2) Rewriting methods in the interface (such as open, close, read, write, destroy, gc) to define the life cycle and storage method of session data; 3) Register a custom session processor in a PHP script and start the session. This allows data to be stored in media such as MySQL and Redis to improve performance, security and scalability.

SessionID is a mechanism used in web applications to track user session status. 1. It is a randomly generated string used to maintain user's identity information during multiple interactions between the user and the server. 2. The server generates and sends it to the client through cookies or URL parameters to help identify and associate these requests in multiple requests of the user. 3. Generation usually uses random algorithms to ensure uniqueness and unpredictability. 4. In actual development, in-memory databases such as Redis can be used to store session data to improve performance and security.

Managing sessions in stateless environments such as APIs can be achieved by using JWT or cookies. 1. JWT is suitable for statelessness and scalability, but it is large in size when it comes to big data. 2.Cookies are more traditional and easy to implement, but they need to be configured with caution to ensure security.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

SAP NetWeaver Server Adapter for Eclipse
Integrate Eclipse with SAP NetWeaver application server.

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software

EditPlus Chinese cracked version
Small size, syntax highlighting, does not support code prompt function

PhpStorm Mac version
The latest (2018.2.1) professional PHP integrated development tool

SublimeText3 Linux new version
SublimeText3 Linux latest version
