CN107959660A - A kind of static file access method and device based on Nginx - Google Patents

A kind of static file access method and device based on Nginx Download PDF

Info

Publication number
CN107959660A
CN107959660A CN201610902701.3A CN201610902701A CN107959660A CN 107959660 A CN107959660 A CN 107959660A CN 201610902701 A CN201610902701 A CN 201610902701A CN 107959660 A CN107959660 A CN 107959660A
Authority
CN
China
Prior art keywords
url
encryption
nginx
page
static file
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
CN201610902701.3A
Other languages
Chinese (zh)
Inventor
胡飞飞
卫伟
张家明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to CN201610902701.3A priority Critical patent/CN107959660A/en
Publication of CN107959660A publication Critical patent/CN107959660A/en
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1441—Countermeasures against malicious traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Storage Device Security (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The invention discloses a kind of static file access method and device based on Nginx.This method includes the step of application server side performs：Receive the accessing page request that client is sent；Determine the corresponding page of accessing page request；Original URL is included in the page；After the original URL included in the page is encrypted, the page is returned into client.This method includes the step of Nginx server sides perform：Receive the URL by encryption that client is sent；The URL of encryption is decrypted, obtains original URL；The corresponding static files of original URL are obtained, and by the data sending in static file to client.Storage path of the static file in Nginx servers is encrypted application server of the present invention, the URL of ciphertext form is sent to client, client is set to access the static file in Nginx servers according to the URL of ciphertext form, and then avoid intercept and capture URL after caused by leaking data the problem of, lifted Nginx servers security.

Description

A kind of static file access method and device based on Nginx
Technical field
The present invention relates to Internet technical field, more particularly to a kind of static file access method based on Nginx and Device.
Background technology
The fast development of internet brings facility for life, but also exposes many problems at the same time, wherein information leakage, The security incidents such as loss of data are commonplace.Sound security protection is established, the loophole protection on basis is carried out, has become interconnection Net field urgent problem to be solved.
At present, most of internet platforms or application have been set up good for the sensitive informations such as user name, password aspect Good awareness of safety, uses encryption technology, to prevent the malice of hacker from stealing during sensitive information is transmitted.But In the prior art, plaintext transmission is used for not being related to the data of sensitive information, such as：Access JS (JavaScript) file, Access address when JPG (Joint Photograhic Experts Group, joint photographic experts group) file, system information Using plaintext transmission.Since the data of plaintext transmission do not pass through any encryption, so access during customer access network Address is easily obtained by hacker, causes leaking data, and for data once revealing, the consequence brought will be hardly imaginable.
The content of the invention
The present invention a kind of static file access method and device based on Nginx, to solve in the prior art, carrying out During network access, the problem of be easy to causeing leaking data is not encrypted to access address.
In order to solve the above-mentioned technical problem, the present invention solves by the following technical programs：
The present invention provides a kind of static file access method based on Nginx, the step of execution in application server side Including：Receive the accessing page request that client is sent；Determine the corresponding page of the accessing page request；Wherein, the page Include original uniform resource position mark URL in face, the corresponding static file of the original URL is stored in Nginx servers；It is right After the original URL included in the page is encrypted, the page is returned into the client, so that the client End accesses the static file stored in the Nginx servers according to the RL of encryption.
Wherein, the original URL included in the page is encrypted, including：To the URL included in the page Carry out multiple encryption.
Wherein, the original URL included in the page is encrypted, including：In the original URL, to quiet Storage path of the state file in Nginx servers is encrypted.
Present invention also offers a kind of static file access method based on Nginx, in the step that Nginx server sides perform Suddenly include：Receive the URL by encryption that client is sent；The URL of the encryption is decrypted, is obtained Original URL；The corresponding static files of the original URL are obtained, and give the data sending in the static file to the client End.
Wherein, the URL of the encryption is decrypted, obtains original URL, including：If at the encryption The URL of reason is that application server obtains the multiple encryption of original URL progress, then the URL of the encryption is carried out Multiple decryption processing, obtains original URL.
Wherein, the URL of the encryption is decrypted, including：In the URL of the encryption, to quiet Storage path of the state file in Nginx servers is decrypted.
The present invention provides a kind of static file access mechanism based on Nginx, application server side is arranged on, including： First receiving module, for receiving the accessing page request of client transmission；Determining module, for determining that the page access please Seek the corresponding page；Wherein, original uniform resource position mark URL is included in the page, the original URL is corresponding static literary Part is stored in Nginx servers；Encrypting module, will after the original URL included in the page is encrypted The page returns to the client, so that the client is accessed in the Nginx servers according to the URL of encryption The static file of storage.
Wherein, the encrypting module, for carrying out multiple encryption to the original URL included in the page.
Wherein, the encrypting module, in the original URL, to storage of the static file in Nginx servers Path is encrypted.
Present invention also offers a kind of static file access mechanism based on Nginx, Nginx server sides are arranged on, are wrapped Include：Second receiving module, for receiving the URL by encryption of client transmission；Deciphering module, for the encryption The URL of processing is decrypted, and obtains original URL；Acquisition module, for obtaining the corresponding static files of the original URL, And give the data sending in the static file to the client.
Wherein, the deciphering module, for being that application server is more to original URL progress in the URL of the encryption In the case that secondary encryption obtains, multiple decryption processing is carried out to the URL of the encryption, obtains original URL.
Wherein, the deciphering module, in the URL of the encryption, to static file in Nginx servers Storage path be decrypted.
The present invention has the beneficial effect that：
The original URL of ciphertext form is sent to client by application server of the present invention, makes client according to ciphertext form Original URL access static file in Nginx servers, and then avoid intercept and capture after original URL caused by leaking data Problem, lifts the security of Nginx servers.
Brief description of the drawings
Fig. 1 is the static file access method flow chart based on Nginx according to a first embodiment of the present invention；
Fig. 2 is the static file access method flow chart based on Nginx according to a second embodiment of the present invention；
Fig. 3 is the static file access method flow chart based on Nginx according to a third embodiment of the present invention；
Fig. 4 is the static file access method schematic diagram based on Nginx according to a third embodiment of the present invention；
Fig. 5 is the static file access mechanism structure chart based on Nginx according to a fourth embodiment of the present invention；
Fig. 6 is the static file access mechanism structure chart based on Nginx according to a fifth embodiment of the present invention.
Embodiment
Below in conjunction with attached drawing and embodiment, the present invention will be described in further detail.It is it should be appreciated that described herein Specific embodiment only to explain the present invention, not limit the present invention.
Embodiment one
The present embodiment provides a kind of static file access method based on Nginx performed in application server side.At this Application server is used to provide application or platform service in embodiment, and application server deposits the static file for needing to store in advance Storage is in Nginx servers.
Fig. 1 is the static file access method flow chart based on Nginx according to a first embodiment of the present invention.
Step S110, receives the accessing page request that client is sent.
In the present embodiment, accessing page request is used for the content for asking accession page.
Client is pre-installed in terminal.Client is, for example, browser.Terminal is, for example, smart mobile phone, and tablet is electric Brain, desktop computer etc..
Step S120, determines the corresponding page of the accessing page request；Wherein, original URL is included in the page, this is original The corresponding static files of URL are stored in Nginx servers.
The domain name addresses that user inputs in client-side is carried in the accessing page request；To in the accessing page request Domain name addresses carry out domain name mapping, obtain the corresponding page of the domain name addresses, the original of multiple static resources included in the page Beginning URL (Uniform Resource Locator, universal resource locator).
Static file is also known as static resource.Data in static file can be loaded into client, and then show use Family.Static file can be JS (JavaScript) script, CSS (Cascading Style Sheets, cascading style sheets), figure The files such as piece.
In the present embodiment, Nginx servers are used to store static file, there is provided static file service.URL is static text The storage address of part, URL include：The IP address of Nginx servers, the port numbers and static file of Nginx servers exist Storage path in Nginx servers.
Such as：The domain name addresses that the accessing page request that client is sent carries is youku.com, and applications client is found The corresponding pages of youku.com are youku.com's homepage, show youku.com's homepage in the client, you can see in youku.com's homepage more Bar links, such as video link, but in fact, every is linked as an original URL, and the corresponding static resource of original URL is stored In Nginx servers, as the corresponding video resource of video link is stored in Nginx servers, clicking on original URL can be from Nginx servers obtain the corresponding static files of the original URL.
Step S130, after the original URL included in the page is encrypted, client is returned to by the page, So that client accesses the static file stored in Nginx servers according to the URL of encryption.
In the present embodiment, before the page is returned to client, place is encrypted to the original URL included in the page Reason, in this way, the original URL in the page is ciphertext form, the original URL for avoiding plaintext version be easy to cause asking for leaking data Topic, improves Information Security.
Using default Encryption Algorithm, original URL is encrypted, and will be sent out comprising the page of encrypted URL Give client.The species of Encryption Algorithm includes but not limited to：MD5 (Message Digest Algorithm 5, eap-message digest Algorithm the 5th edition) algorithm, RSA cryptographic algorithms, DES (Data Encryption Algorithm, data encryption algorithm), BASE64 encryption algorithms, mutation BASE64 encryption algorithms.
In the present embodiment, multiple encryption can be carried out to the original URL included in the page, and will be included through excessive The page of the original URL of secondary encryption is sent to client.Such as：Place is first encrypted to original URL using DES algorithms Reason, obtains one-time pad encryption URL, then using BASE64 encryption algorithms, one-time pad encryption URL is encrypted again, obtains two Secondary encryption URL, client is sent to by the page comprising secondary encryption URL.
In the present embodiment, storage path of the static file in Nginx servers can be carried out in original URL Encryption, and the number of encryption is one or many.Such as：Original URL is http://10.47.182.70:8902/ Task/final/tuwen/2015072310204764.html, 10.47.182.70 be Nginx servers IP address, 8902 For the port numbers of Nginx servers, task/final/tuwen/2015072310204764 services for static file in Nginx Storage path in device, before the page is sent to client, to the storing place of static file in the original URL in the page Location task/final/tuwen/2015072310204764 is encrypted.Further, the number of encryption is once Or repeatedly.
The present embodiment strengthens safety prevention measure to the static file being stored in Nginx servers, and static file is existed Storage path in Nginx servers is encrypted, and the original URL of ciphertext form is sent to client, avoids intercepting and capturing original Caused by after URL the problem of leaking data, the security of Nginx servers is lifted.
Embodiment two
The present embodiment provides a kind of static file access method based on Nginx performed in Nginx servers, such as Fig. 2 It is the static file access method flow chart based on Nginx according to a second embodiment of the present invention.
Step S210, receives the URL by encryption that client is sent.
The URL of encryption is obtained after original URL is encrypted in application server.
Original URL refers to the URL included in the corresponding page of accessing page request.
Specifically, client loads the page after the page of application server return is received, so as to by page exhibition Show to user, user can click on the link in the page, and then trigger the transmission of URL, to obtain the link from Nginx servers Corresponding static file, that is to say the corresponding static files of the URL, since application server has carried out at encryption original URL Reason, so the URL that client is sent is the original URL of ciphertext form.
Step S220, is decrypted the URL of the encryption, obtains original URL.
Using default decipherment algorithm, the URL of encryption is decrypted, obtains original URL.The decipherment algorithm It is corresponding with the Encryption Algorithm that application server side uses.Such as：Encryption Algorithm and decipherment algorithm are symmetry algorithm.
Multiple encryption carried out to original URL obtain if the URL of the encryption is application server, pair plus The URL of close processing carries out multiple decryption processing, obtains original URL.
Such as：The URL of encryption is to carry out BASE64 codings after application server first carries out original URL des encryption It is obtaining as a result, due to the inverse process that decryption processing is encryption, so first carrying out that BASE64 is counter to be compiled to the URL of encryption Code, it is rear to carry out DES decryption processings, obtain original URL.
In the present embodiment, in the URL of encryption, to storage path of the static file in Nginx servers into Row decryption processing.Such as：The URL of encryption is http://10.47.182.70:8902/xyCXtdt_ BqxGHyu88VTHARvvbLBTDcQEipLWJO_LecV52I2Xmcd XlwA, wherein, 10.47.182.70 services for Nginx The IP address of device, 8902 be Nginx servers port numbers, xyCXtdt_BqxGHyu88VTHARvvbLBTDcQEipLWJO_ LecV52I2XmcdXlwA is the storage path of the static file after encryption, then, to xyCXtdt_ BqxGHyu88VTHARvvbLBTDcQEipLWJO_LecV52I2XmcdXlwA is decrypted.Further, according to application The encryption number of server and the Encryption Algorithm of use, perform one or many decryption processings.
Step S230, obtains the corresponding static files of original URL, and by the data sending in static file to client.
According to the storage path of static file in original URL, corresponding static file is obtained in Nginx servers, and The static file is sent to client, to be shown in the client.
Such as：Portal uses server of the Nginx servers as storage static file, and static file can store Style sheet；The storage path of static file can be encrypted and encoded and (encrypted twice) by portal, form encryption URL；Portal provides encryption URL to the user, when such user accesses the style sheet of portal, it will accesses encryption URL；Nginx servers carry out the encryption URL Gray code and decryption conversion (decrypting twice), encryption URL are converted to original URL, and access according to original URL the local hard drive of Nginx servers, finds the corresponding static files of original URL, and by static state The content of file returns to user, to be shown in the client.
Through this embodiment, client accesses the static file in Nginx servers according to the ULR of ciphertext form.URL exists Transmitted between client, application server and Nginx servers with ciphertext form, ensure that original URL is not illegally stolen, prevent The problem of data safety that leaking data triggers.
Embodiment three
The present embodiment provides a kind of more specific static file access method based on Nginx.Fig. 3 is according to the present invention The static file access method flow chart based on Nginx of 3rd embodiment.Fig. 4 be according to a third embodiment of the present invention based on The static file access method schematic diagram of Nginx.
Step S310, application server configuration static file, and static file storage to Nginx servers, Nginx are taken Business device returns to the corresponding original URL of static file to application server.
Step S320, client sends accessing page request to application server, to ask the content of accession page.
Application server can obtain the corresponding page of accessing page request by carrying out domain name mapping to accessing page request Face, such as：Youku.com's homepage, Sohu's homepage, Sina's homepage.Include the corresponding URL of multiple static files in the page.
Step S330, application server carry out des encryption to the original URL included in the page, obtain DES ciphertexts.
Application server carries out des encryption (one-time pad encryption) to the storage path in each original URL, and the key used is Decryption_key, obtains DES ciphertexts.Such as：Original URL is http://10.47.182.70:8902/task/final/ Tuwen/2015072310204764.html, key 12345678, the DES ciphertexts obtained after des encryption is handled are：
http://10.47.182.70:8902/ C72097B5DB7F6AC461F2BBCF154C711BEF6CB053DC448A92D624EFCB79C579D88D9799C75797。
Step S340, application server carry out mutation BASE64 codings to DES ciphertexts, obtain encryption URL.
Application server is to (secondary by the storage path progress mutation BASE64 codings of one-time pad encryption in DES ciphertexts Encryption), obtain encryption URL.
Such as：DES ciphertexts are：
http://10.47.182.70:8902/ C72097B5DB7F6AC461F2BBCF154C711BEF6CB053DC448A92D624EFCB 79C579D88D9799C75797, Mutation BASE64 carried out to it encode to obtain encryption URL be：
http://10.47.182.70:8902/xyCXtdt_BqxGHyu88VTHARvvbLBTDcQEipLWJ O_ LecV52I2XmcdXlwA。
The page comprising encryption URL is sent to client by step S350, application server.
Step S360, client access the static file for being stored in Nginx servers by encryption URL.
It is counter to encryption URL progress mutation BASE64 to compile after step S370, Nginx server receives encryption URL Code, obtains DES ciphertexts.
Nginx servers by secondary encrypted storage path in encryption URL to carrying out mutation BASE64 Gray codes.
Such as：Encrypting URL is：
http://10.47.182.70:8902/xyCXtdt_BqxGHyu88VTHARvvbLBTDcQEipLWJ O_ LecV52I2XmcdXlwA, carries out BASE64 Gray codes to encryption URL, obtains DSE ciphertexts：
http://10.47.182.70:8902/ C72097B5DB7F6AC461F2BBCF154C711BEF6CB053DC448A92D624EFCB79C579D88D9799C75797。
Step S380, Nginx server carries out DES decryption to DES ciphertexts, obtains original URL.
Nginx servers and application server are consulted to be used for the key encrypted, decrypted in advance, and are stored in Nginx services In the Nginx configuration files of device.
DES ciphertexts are decrypted in key decryption_key of the Nginx servers in Nginx configuration files, The URL of unencryption is got, i.e., original URL.Wherein, des encryption and the key that uses of DES decryption are identical, all for for 12345678。
Nginx servers by the storage path of one-time pad encryption in DES ciphertexts to carrying out DES decryption.
Such as：DES ciphertexts are：
http://10.47.182.70:8902/ C72097B5DB7F6AC461F2BBCF154C711BEF6CB053DC448A92D624EFCB 79C579D88D9799C75797, DES decryption is carried out to the DES ciphertexts, can obtain original URL is：
http://10.47.182.70:8902/task/final/tuwen/2015072310204764.html。
Step S390, Nginx server accesses local hard drive according to original URL, finds corresponding static file, and should Data in static file return to client.
In the present embodiment, application server is original URL des encryption conversion and mutation BASE64 transcoding, coding transforms, Original URL is converted to encryption URL, and application server provides encryption URL to the user；User is deposited in by encrypting URL access The fileinfo of Nginx server ends, Nginx carry out BASE64 Gray codes and DES decryption transformations to encryption URL, encryption URL Original URL is converted to, and local hard drive is accessed according to original URL, corresponding static file is found and returns to static file content.
Example IV
The present embodiment provides a kind of static file access mechanism based on Nginx for being arranged on application server side, Fig. 5 is The static file access mechanism structure chart based on Nginx according to a fourth embodiment of the present invention.
This is arranged on the static file access mechanism based on Nginx of application server side, including：
First receiving module 510, for receiving the accessing page request of client transmission.
Determining module 520, for determining the corresponding page of the accessing page request；Wherein, original is included in the page Beginning uniform resource position mark URL, the corresponding static file of the original URL are stored in Nginx servers.
Encrypting module 530, after the original URL included in the page is encrypted, the page is returned Back to the client, so that the client in the URL of the encryption access Nginx servers according to storing Static file.
In one embodiment, encrypting module 530, for repeatedly being encrypted to the original URL included in the page Processing.
In another embodiment, encrypting module 530, in the original URL, being serviced in Nginx static file Storage path in device is encrypted.
The function of device described in the present embodiment is described in the embodiment of the method shown in Fig. 1 and Fig. 3, therefore Not detailed part, may refer to the related description in previous embodiment, this will not be repeated here in the description of the present embodiment.
Embodiment five
The present embodiment provides a kind of static file access mechanism based on Nginx for being arranged on Nginx server sides, Fig. 6 It is the static file access mechanism structure chart based on Nginx according to a fifth embodiment of the present invention.
This is arranged on the static file access mechanism based on Nginx of Nginx server sides, including：
Second receiving module 610, for receiving the URL by encryption of client transmission.
Deciphering module 620, for the URL of the encryption to be decrypted, obtains original URL.
Acquisition module 630, for obtaining the corresponding static files of the original URL, and by the number in the static file According to being sent to the client.
In one embodiment, deciphering module 620, for being application server to original in the URL of the encryption In the case that the multiple encryption of URL progress obtains, multiple decryption processing is carried out to the URL of the encryption, is obtained original URL。
In another embodiment, deciphering module 620, in the URL of the encryption, existing to static file Storage path in Nginx servers is decrypted.
The function of device described in the present embodiment is described in the embodiment of the method shown in Fig. 2 and Fig. 3, therefore Not detailed part, may refer to the related description in previous embodiment, this will not be repeated here in the description of the present embodiment.
Although being example purpose, the preferred embodiment of the present invention is had been disclosed for, those skilled in the art will recognize Various improvement, increase and substitution are also possible, and therefore, the scope of the present invention should be not limited to above-described embodiment.

Claims (12)

1. a kind of static file access method based on Nginx, it is characterised in that wrapped the step of application server side performs Include：
Receive the accessing page request that client is sent；
Determine the corresponding page of the accessing page request；Wherein, original uniform resource position mark URL is included in the page, The corresponding static file of the original URL is stored in Nginx servers；
After the original URL included in the page is encrypted, the page is returned into the client, so that institute State client and the static file stored in the Nginx servers is accessed according to the URL of encryption.
2. the method as described in claim 1, it is characterised in that the original URL included in the page is encrypted, Including：
Multiple encryption is carried out to the original URL included in the page.
3. method as claimed in claim 1 or 2, it is characterised in that place is encrypted to the original URL included in the page Reason, including：
In the original URL, storage path of the static file in Nginx servers is encrypted.
4. a kind of static file access method based on Nginx, it is characterised in that wrapped the step of Nginx server sides perform Include：
Receive the URL by encryption that client is sent；
The URL of the encryption is decrypted, obtains original URL；
The corresponding static files of the original URL are obtained, and give the data sending in the static file to the client.
5. method as claimed in claim 4, it is characterised in that be decrypted, obtain former to the URL of the encryption Beginning URL, including：
The multiple encryption of original URL progress is obtained if the URL of the encryption is application server, to described The URL of encryption carries out multiple decryption processing, obtains original URL.
6. method as described in claim 4 or 5, it is characterised in that be decrypted, wrap to the URL of the encryption Include：
In the URL of the encryption, storage path of the static file in Nginx servers is decrypted.
A kind of 7. static file access mechanism based on Nginx, it is characterised in that application server side is arranged on, including：
First receiving module, for receiving the accessing page request of client transmission；
Determining module, for determining the corresponding page of the accessing page request；Wherein, original URL is included in the page；Its In, the corresponding static file of the original URL is stored in Nginx servers；
Encrypting module, after the original URL included in the page is encrypted, the page is returned to described Client, so that the client accesses the static text stored in the Nginx servers according to the URL of encryption Part.
8. device as claimed in claim 7, it is characterised in that the encrypting module, for the original to being included in the page Beginning URL carries out multiple encryption.
9. device as claimed in claim 7 or 8, it is characterised in that the encrypting module is right in the original URL Storage path of the static file in Nginx servers is encrypted.
A kind of 10. static file access mechanism based on Nginx, it is characterised in that Nginx server sides are arranged on, including：
Second receiving module, for receiving the URL by encryption of client transmission；
Deciphering module, for the URL of the encryption to be decrypted, obtains original URL；
Acquisition module, for obtaining the corresponding static files of the original URL, and the data sending in the static file is given The client.
11. device as claimed in claim 10, it is characterised in that the deciphering module, for the URL in the encryption It is that in the case that application server obtains the multiple encryption of original URL progress, the URL of the encryption is carried out repeatedly Decryption processing, obtains original URL.
12. the device as described in claim 10 or 11, it is characterised in that the deciphering module, in the encryption URL in, storage path of the static file in Nginx servers is decrypted.
CN201610902701.3A 2016-10-17 2016-10-17 A kind of static file access method and device based on Nginx Withdrawn CN107959660A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610902701.3A CN107959660A (en) 2016-10-17 2016-10-17 A kind of static file access method and device based on Nginx

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610902701.3A CN107959660A (en) 2016-10-17 2016-10-17 A kind of static file access method and device based on Nginx

Publications (1)

Publication Number Publication Date
CN107959660A true CN107959660A (en) 2018-04-24

Family

ID=61953478

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610902701.3A Withdrawn CN107959660A (en) 2016-10-17 2016-10-17 A kind of static file access method and device based on Nginx

Country Status (1)

Country Link
CN (1) CN107959660A (en)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108737531A (en) * 2018-05-11 2018-11-02 北京奇艺世纪科技有限公司 A kind of method and apparatus of business processing
CN109325192A (en) * 2018-10-11 2019-02-12 网宿科技股份有限公司 A kind of method and apparatus of the anti-shielding of advertisement
CN109977330A (en) * 2019-03-12 2019-07-05 平安科技（深圳）有限公司 Web access method and relevant device based on dynamic access path
CN110134391A (en) * 2019-04-28 2019-08-16 苏宁易购集团股份有限公司 A kind of adaptation method and device for the mobile page
CN110263533A (en) * 2019-04-28 2019-09-20 清华大学 Safe web page means of defence
CN110365676A (en) * 2019-07-12 2019-10-22 浙江智贝信息科技有限公司 Guard method and system are obscured in a kind of encryption of website static page
CN110515631A (en) * 2019-08-23 2019-11-29 掌阅科技股份有限公司 Using the generation method of installation data packet, server and computer storage medium
CN111541758A (en) * 2020-04-17 2020-08-14 支付宝(杭州)信息技术有限公司 Page updating method and device
CN111666580A (en) * 2020-06-24 2020-09-15 北京航天数据股份有限公司 File encryption method, file decryption method and file encryption device
CN111756847A (en) * 2020-06-28 2020-10-09 北京百度网讯科技有限公司 Method and device for supporting https protocol by website
CN113055344A (en) * 2019-12-27 2021-06-29 贵州白山云科技股份有限公司 Scheduling method, device, medium and equipment
CN113609425A (en) * 2021-07-15 2021-11-05 西安四叶草信息技术有限公司 Webpage data processing method and system

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7127609B2 (en) * 2001-01-12 2006-10-24 Siemens Medical Solutions Health Services Corporation System and user interface for adaptively processing and communicating URL data between applications
CN102325225A (en) * 2011-09-20 2012-01-18 北京鹏润鸿途科技有限公司 Method and device for playing video of mobile phone website
CN102946392A (en) * 2012-11-15 2013-02-27 亚信联创科技（中国）有限公司 URL (Uniform Resource Locator) data encrypted transmission method and system
CN103139204A (en) * 2012-12-19 2013-06-05 姚爱军 Network identifying code method and system
CN103902916A (en) * 2012-12-25 2014-07-02 联想(北京)有限公司 Processing method and electronic device
US20150205766A1 (en) * 2012-03-08 2015-07-23 Google Inc. Serving combined resources to a browser client
CN105516208A (en) * 2016-01-28 2016-04-20 邱铭钗 WEB site link dynamic hiding method and device capable of effectively preventing network attacks

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7127609B2 (en) * 2001-01-12 2006-10-24 Siemens Medical Solutions Health Services Corporation System and user interface for adaptively processing and communicating URL data between applications
CN102325225A (en) * 2011-09-20 2012-01-18 北京鹏润鸿途科技有限公司 Method and device for playing video of mobile phone website
US20150205766A1 (en) * 2012-03-08 2015-07-23 Google Inc. Serving combined resources to a browser client
CN102946392A (en) * 2012-11-15 2013-02-27 亚信联创科技（中国）有限公司 URL (Uniform Resource Locator) data encrypted transmission method and system
CN103139204A (en) * 2012-12-19 2013-06-05 姚爱军 Network identifying code method and system
CN103902916A (en) * 2012-12-25 2014-07-02 联想(北京)有限公司 Processing method and electronic device
CN105516208A (en) * 2016-01-28 2016-04-20 邱铭钗 WEB site link dynamic hiding method and device capable of effectively preventing network attacks

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108737531A (en) * 2018-05-11 2018-11-02 北京奇艺世纪科技有限公司 A kind of method and apparatus of business processing
CN109325192A (en) * 2018-10-11 2019-02-12 网宿科技股份有限公司 A kind of method and apparatus of the anti-shielding of advertisement
CN109977330A (en) * 2019-03-12 2019-07-05 平安科技（深圳）有限公司 Web access method and relevant device based on dynamic access path
CN110134391A (en) * 2019-04-28 2019-08-16 苏宁易购集团股份有限公司 A kind of adaptation method and device for the mobile page
CN110263533A (en) * 2019-04-28 2019-09-20 清华大学 Safe web page means of defence
CN110365676A (en) * 2019-07-12 2019-10-22 浙江智贝信息科技有限公司 Guard method and system are obscured in a kind of encryption of website static page
CN110515631A (en) * 2019-08-23 2019-11-29 掌阅科技股份有限公司 Using the generation method of installation data packet, server and computer storage medium
CN113055344A (en) * 2019-12-27 2021-06-29 贵州白山云科技股份有限公司 Scheduling method, device, medium and equipment
CN111541758A (en) * 2020-04-17 2020-08-14 支付宝(杭州)信息技术有限公司 Page updating method and device
CN111666580A (en) * 2020-06-24 2020-09-15 北京航天数据股份有限公司 File encryption method, file decryption method and file encryption device
CN111756847A (en) * 2020-06-28 2020-10-09 北京百度网讯科技有限公司 Method and device for supporting https protocol by website
CN111756847B (en) * 2020-06-28 2023-05-09 北京百度网讯科技有限公司 Method and device for supporting https protocol by website
CN113609425A (en) * 2021-07-15 2021-11-05 西安四叶草信息技术有限公司 Webpage data processing method and system

Similar Documents

Publication Publication Date Title
CN107959660A (en) A kind of static file access method and device based on Nginx
CN112333198B (en) Secure cross-domain login method, system and server
US9836612B2 (en) Protecting data
US11741185B1 (en) Managing content uploads
US10951595B2 (en) Method, system and apparatus for storing website private key plaintext
US10904227B2 (en) Web form protection
CN104217173B (en) A kind of data and file encrypting method for browser
CN104283903B (en) The method for down loading and device of file
US11770385B2 (en) Systems and methods for malicious client detection through property analysis
CN104580086A (en) Information transmission method, client side, server and system
CN113179323B (en) HTTPS request processing method, device and system for load balancing equipment
CN109409045A (en) Browser automated log on account number safety guard method and device
US8789177B1 (en) Method and system for automatically obtaining web page content in the presence of redirects
CN112287372A (en) Method and apparatus for protecting clipboard privacy
JP2010072916A (en) Data protection system and data protection method
CN112199622A (en) Page jump method, system and storage medium
CN104901951B (en) Code data processing based on mobile terminal and exchange method in a kind of Web applications
JP2006216002A (en) Url security system
CN114978637A (en) Message processing method and device
CN107026828A (en) A kind of anti-stealing link method cached based on internet and internet caching
CN109343971B (en) Browser data transmission method and device based on cache technology
CN104506530A (en) Network data processing method and device and data transmission method and device
US10855513B2 (en) Information pushing method, device and computer readable storage medium
CN106470186A (en) A kind of to redirect the method that mode accesses third party's resource
KR102661484B1 (en) Fraud prevention in aggregated network measurements

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
WW01 Invention patent application withdrawn after publication
WW01 Invention patent application withdrawn after publication

Application publication date: 20180424