Network reloading method and device for cross-border e-commerce browser, equipment and medium

Abstract

The invention provides a network reloading method and device for a cross-border e-commerce browser, equipment and a medium. The method comprises the steps that the cross-border e-commerce browser receives a server configuration file updating notification; after the cross-border e-commerce browser receives the server configuration file, analyzing the server configuration file into a configuration object which can be identified by the cross-border e-commerce browser; generating a replacement configuration file based on the configuration object, obtaining an idle port, creating and operating a new service instance based on the replacement configuration file, and obtaining an exit IP of the new service instance; verifying whether the exit IP is consistent with a preset IP in the replacement configuration file, if yes, updating a monitoring port in the local configuration file to the replacement configuration file, storing the local configuration file, closing an old service instance, setting a new service instance as a global service instance, and completing network reloading; the service continuity is ensured, the risk of configuration updating and the user operation cost are reduced to the maximum extent, and the method is particularly suitable for multi-shop, high-concurrency and strong-network-dependence service scenes.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of network communication, in particular to a network reloading method, device, equipment and medium for cross-border e-commerce browser. BACKGROUND

[0002] In the field of cross-border e-commerce, many sellers conduct business with the help of cross-border e-commerce browsers, and manage their shops through Zhuba shops. Cross-border e-commerce browsers include Zhuba browser and the like. However, in the process of use, some users may encounter abnormal network environment of the shop. The occurrence of such problems may be caused by various factors, such as IP protocol failure, DNS pollution, etc., which will result in abnormal use or failure of the shop.

[0003] When users encounter such network environment problems, they will contact our customer service team. The customer service personnel will respond quickly, diagnose the problem, and take appropriate repair measures to restore the network environment of the shop. After the repair is completed, in order to ensure the repair effect, the user usually needs to reopen the shop to make the update of the network environment take effect.

[0004] However, in the actual operation process, we found that this requirement brings certain trouble to the users. Some users may bind dozens or even hundreds of shops with the same IP, or open a large number of tabs at the same time. In addition, some users may be in the process of submitting a form, and closing the shop will cause the loss of the form content. If the user restarts all the shops, he / she needs to fill in the form again, which undoubtedly increases the time cost and operation cost of the user, and brings great inconvenience to the user. SUMMARY

[0005] The technical problem to be solved by the present application is to provide a network reloading method, device, equipment and medium for cross-border e-commerce browser, so that the shop website opened by the user is exempted from restarting, and the user can use it conveniently.

[0006] In a first aspect, the present application provides a network reloading method for cross-border e-commerce browser, comprising the following steps: Step 1: The cross-border e-commerce browser receives the service end configuration file update notification, and triggers the network reloading process; Step 2: After receiving the service end configuration file, the cross-border e-commerce browser parses it into a configuration object recognizable by the cross-border e-commerce browser; Step 3: Based on the configuration object, the local configuration file of the cross-border e-commerce browser is updated, and a replacement configuration file is generated; Step 4, obtaining an idle port, creating and running a new service instance based on a replacement configuration file, sending a proxy request to the new service instance, obtaining an egress IP of the new service instance, verifying whether the egress IP is consistent with a preset IP in the replacement configuration file, if not, terminating network reloading and ending the step, if yes, entering step 5; Step 5, updating a listening port in a local configuration file to the replacement configuration file, saving the local configuration file, closing an old service instance, setting the new service instance as a global service instance, and completing network reloading.

[0007] Step 6, after network reloading, silently implementing the latest configuration.

[0008] In a second aspect, the present application provides a network reloading device for a cross-border e-commerce browser, comprising: A triggering flow module, the cross-border e-commerce browser receives a service end configuration file update notification and triggers a network reloading flow; A recognition module, after the cross-border e-commerce browser receives the service end configuration file, the configuration file is parsed into a configuration object recognizable by the cross-border e-commerce browser; A replacement configuration file module, based on the configuration object, a local configuration file of the cross-border e-commerce browser is updated, and a replacement configuration file is generated; A test module, obtaining an idle port, creating and running a new service instance based on a replacement configuration file, sending a proxy request to the new service instance, obtaining an egress IP of the new service instance, verifying whether the egress IP is consistent with a preset IP in the replacement configuration file, if not, terminating network reloading and ending the step, if yes, entering an update module; The update module, updating a listening port in a local configuration file to the replacement configuration file, saving the local configuration file, closing an old service instance, setting the new service instance as a global service instance, and completing network reloading.

[0009] A network reloading module, after network reloading, silently implementing the latest configuration.

[0010] In a third aspect, the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method of the first aspect when executing the program.

[0011] In a fourth aspect, the present application provides a computer readable storage medium, which stores a computer program, and the program is executed by a processor to implement the method of the first aspect.

[0012] The one or more technical solutions provided by the present application have at least the following technical effects or advantages: 1. Smooth and imperceptible switching, reducing service interruption By the process of "starting a new service on a temporary port → verifying validity → closing the old service → switching to the original port", seamless connection of new and old services is achieved. Users (such as stores) do not need to restart to use the new configuration, avoiding service interruption caused by traditional restart methods, especially suitable for cross-border e-commerce scenarios that require high continuity (such as form submission, multi-store management, etc.).

[0013] 2. Strict pre-validation to reduce update risk The process includes multiple validation mechanisms: Configuration decryption and parsing validation to ensure that the input configuration format is legal; Consistency check of proxy exit IP and expected IP to avoid service anomalies caused by network configuration errors; Idle port acquisition retry and IP acquisition retry to improve environmental adaptability.

[0014] These checks can intercept most errors before service switching, reducing the probability of configuration update failure.

[0015] 3. Resource safety recovery to avoid memory leaks Complete rollback logic is preset through the defer mechanism: If the new service fails to start, the new service instance will be automatically closed; Before replacing the old service, all connections of the old service are closed to ensure that resources such as ports and network connections are released.

[0016] This "clean up before replacement" design avoids memory leaks or port occupation caused by resource residues.

[0017] 4. Concurrent safety design to support multi-scene calling Mutex is used to ensure atomicity during hot reloading, preventing conflicts between new and old services, configuration chaos, and other issues that may occur when multiple threads are concurrently called, ensuring that updates can still be performed stably in high-concurrency scenarios.

[0018] 5. Strong traceability for easy problem troubleshooting Key node logs (such as decryption success, port replacement, IP validation results, etc.) are recorded throughout the process, and logs are asynchronously uploaded after the process ends (whether successful or failed). These logs can be used to trace exceptions during the update process, quickly locate configuration errors, network problems, and other root causes.

[0019] In summary, this implementation combines "smooth switching + strict validation + resource safety + log tracing" to maximize the reduction of configuration update risks and user operation costs while ensuring service continuity, especially suitable for business scenarios that require multi-store, high concurrency, and strong network dependence.

[0020] The above description is only a summary of the technical solutions of the present application. In order to more clearly understand the technical means of the present application, the contents of the specification can be implemented, and in order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the following specific embodiments of the present application are described. BRIEF DESCRIPTION OF DRAWINGS

[0021] The present application will be further described below with reference to the accompanying drawings and embodiments.

[0022] Figure 1 The flowchart of the method in the first embodiment of the present application is shown. Figure 2 The structure diagram of the device in the second embodiment of the present application is shown. DETAILED DESCRIPTION

[0023] The technical solutions in the embodiments of the present application have the following general ideas: 1. Receive the hot update notification of the service end and prepare to perform network reload 2. After receiving the new configuration information, initialize and configure the analysis 3. Get new idle ports and start the services that need to be started 4. Create and run new services, get proxy export IP, and verify the correctness of the IP address 5. Service switching (save the old configuration before reload, close the old service connection, replace the inbound configuration, set the new service), perform network reload 6. After network reload, the store does not need to restart, and the latest configuration is effective in silence.

[0024] The core code of the above implementation is as follows: func (s *service) GatewayReload(reqID string, data string) (err error) { s.mu.Lock() defer s.mu.Unlock() var ( newService *service originalPort int runner *v2ray.Runner ) defer func() { if rvr := recover(); rvr!= nil { Recover(rvr) logrus.Warnf("GatewayReload panic: %v", rvr) err = errors.New("system error") } }() decryptConfig, err := utils.AESDecryptPKCS7(data) if err != nil { return err } logrus.Infof("AesDecryptPKCS7 success!") logrus.Debugf("config: %v", string(decryptConfig)) cfg, err := config.Parse(decryptConfig, []byte(data)) if err != nil { return err } logrus.Infof("Parse success!") defer func() { / / Upload logs go s.uploadLogs(cfg, newService, err) }() InitModules(cfg) logrus.Infof("InitModules success!") originalPort, err = s.replaceAndGetListenInfo(cfg) if err != nil { return err } if cfg.RunV2ray { runner = v2ray.NewRunner() err = runner.Start(cfg) if err != nil { return err } logrus.Infof("v2ray start success!") defer func() { if err!= nil { runner.Shutdown() } }() } newService, err = NewAndRun(cfg) if err!= nil { return err } logrus.Infof("NewAndRun success!") defer func() { if err!= nil { newService.Close() } }() time.Sleep(100 * time.Millisecond) ip := GetProxyOutIp(cfg) if ip == "" { err = fmt.Errorf("GetProxyOutIp failed") return err } logrus.Infof("GetProxyOutIp success!") if ip!= constant.GetProxyIp() { err = fmt.Errorf("ip: %s!= cfg.ProxyIP: %s", ip,constant.GetProxyIp()) return err } logrus.Infof("out ip check success!") cfg.Inbound.Port = originalPort if Service != nil { / / First reload if Service.OldConf() == nil { cfg.OldRaw = Service.Conf() } else { cfg.OldRaw = Service.OldConf() } logrus.Infof("save old config success!") if Service.cfg.RunV2ray { v2ray.V2Runner.Shutdown() logrus.Infof("v2ray shutdown success!") } err = Service.CloseAllConnections() if err != nil { return err } Service.Close() logrus.Infof("Close success!") } if cfg.RunV2ray { [[ID=4)) / / runner.Shutdown() / / v2ray.V2Runner = v2ray.NewRunner() )]] / / err = v2ray.V2Runner.Start(cfg) v2ray.V2Runner = runner / / logrus.Infof("v2ray restart success!") } err = newService.ReplaceInbound(cfg) logrus.Infof("ReplaceInbound success!") if err != nil { return err } SetService(newService) logrus.Infof("SetService success!") return nil } func (s *service) replaceAndGetListenInfo(cfg *config.Config)(originalPort int, err error) { var newPort int for i := 0; i < 3; i++ { newPort, err = utlsNet.NewFreePort(false) if err != nil { logrus.Warnf("new free port error: %s i: %d", err, i) continue } break } if newPort == 0 { return 0, fmt.Errorf("no free port") } originalPort = cfg.Inbound.Port cfg.Inbound.Port = newPort return originalPort, nil } func GetProxyOutIp(cfg *config.Config) string { var finished bool resCh := make(chan string) go func() { for i := 0; i < 5; i++ { if finished { logrus.Infof("GetProxyOutIp exit: %v", i) return } go func() { proxyInfo := cfg.Inbound proxyInfo.IP = "127.0.0.1" res, _, err := net.SendHttpRequestByProxy(proxyInfo.Scheme,proxyInfo.IP, cast.ToString(proxyInfo.Port), proxyInfo.Username,proxyInfo.Password, api.GetCheckIpUrls()) if err!= nil { logrus.Warnf("GetProxyOutIp: %v", err) return } if ip := net.FindIP(res); ip!= nil { err = channel.NonBlockSend(resCh, ip.String()) if err!= nil { logrus.Warnf("send out ip error: %v", err) return } else { finished = true } } logrus.Infof("GetProxyOutIp: %s", res) }() time.Sleep(time.Second) } }() val, err := channel.AcceptTimeout(resCh, 5) if err!= nil { logrus.Warnf("GetProxyOutIp: %v", err) return "" } return val } Example

[0025] like Figure 1 As shown, this embodiment provides a network reloading method for a cross-border e-commerce browser, including the following steps: Step 1: The cross-border e-commerce browser receives a server-side configuration file update notification, triggering a network reload process; Step 2: After receiving the server-side configuration file, the cross-border e-commerce browser parses it into a configuration object that the cross-border e-commerce browser can recognize. Step 3: Update the local configuration file of the cross-border e-commerce browser based on the configuration object, and generate a replacement configuration file; Step 4: Obtain an available port, create and run a new service instance based on the replacement configuration file, send a proxy request to the new service instance, and obtain the exit IP of the new service instance; verify whether the exit IP is consistent with the preset IP in the replacement configuration file. If they are inconsistent, terminate network reload and end the step; if they are consistent, proceed to step 5. Step 5: Update the listening port in the local configuration file to the replacement configuration file, save the local configuration file, shut down the old service instance, set the new service instance as the global service instance, and complete the network reload.

[0026] Step 6: After the network is reloaded, the latest configuration will take effect silently.

[0027] In this embodiment, preferably, step 1 specifically involves: the cross-border e-commerce browser receiving a server-side configuration file update notification, triggering a network reload process, adding a mutex lock to the reload process to ensure thread safety, and pre-setting a lock release and global exception capture mechanism.

[0028] In this embodiment, preferably, step 2 specifically involves: after receiving the server-side configuration file, the cross-border e-commerce browser first decrypts it using a set decryption algorithm, and after successful decryption, it parses it into a configuration object that the cross-border e-commerce browser can recognize; at the same time, it registers asynchronous log upload logic to upload network reload results.

[0029] In this embodiment, preferably, step 4 specifically involves: obtaining an idle port, creating and running a new service instance based on the replacement configuration file, and pre-setting new service rollback logic; after waiting for a set time, sending a proxy request to the new service instance to obtain the exit IP of the new service instance; verifying whether the exit IP is consistent with the preset IP in the replacement configuration file; if they are inconsistent, terminating network reload and ending the step; if they are consistent, proceeding to step 5.

[0030] Based on the same inventive concept, the application also provides a device corresponding to the method in embodiment one, which is described in detail in embodiment two. Embodiment

[0031] As shown in the embodiment, a network reloading device for cross-border e-commerce browser is provided, which comprises: Figure 2 A triggering flow module, the cross-border e-commerce browser receives a service end configuration file update notification to trigger a network reloading flow; A recognition module, after the cross-border e-commerce browser receives the service end configuration file, the configuration file is parsed into a configuration object recognizable by the cross-border e-commerce browser; A replacement configuration file module, based on the configuration object, the local configuration file of the cross-border e-commerce browser is updated to generate a replacement configuration file; A test module, an idle port is obtained, a new service instance is created and run based on the replacement configuration file, a proxy request is sent to the new service instance, and an egress IP of the new service instance is obtained; it is verified whether the egress IP is consistent with the preset IP in the replacement configuration file, if not, the network reloading is terminated, and the step is ended; if yes, an update module is entered; The update module updates the listening port in the local configuration file to the replacement configuration file, saves the local configuration file, closes the old service instance, sets the new service instance as a global service instance, and completes the network reloading. A network reloading module, after the network reloading, the latest configuration is silently effective.

[0032] In the embodiment, preferably, the triggering flow module specifically comprises: the cross-border e-commerce browser receives a service end configuration file update notification to trigger a network reloading flow, a mutual exclusion lock is added to the reloading flow to ensure thread safety, and a lock release and global exception capture mechanism are preset.

[0033] In the embodiment, preferably, the recognition module specifically comprises: after the cross-border e-commerce browser receives the service end configuration file, the configuration file is decrypted by setting a decryption algorithm, and after the decryption is successful, the configuration object recognizable by the cross-border e-commerce browser is parsed; at the same time, an asynchronous log uploading logic is registered for uploading the network reloading result.

[0034] In the embodiment, preferably, the test module specifically comprises: an idle port is obtained, a new service instance is created and run based on the replacement configuration file, and a new service rollback logic is preset; after waiting for a set time, a proxy request is sent to the new service instance, and an egress IP of the new service instance is obtained; it is verified whether the egress IP is consistent with the preset IP in the replacement configuration file, if not, the network reloading is terminated, and the step is ended; if yes, an update module is entered.

[0035]

[0036] ​Since the device introduced in the embodiment two is the device used for implementing the method of the embodiment one, the specific structure and the deformation of the device can be understood by the person skilled in the art based on the method introduced in the embodiment one, and thus will not be described here again. The device used for the method of the embodiment one belongs to the scope of the present application.

[0037] Based on the same inventive concept, the present application provides the electronic device embodiment corresponding to the embodiment one, which is described in detail in the embodiment three. Embodiment

[0038] The embodiment provides an electronic device, which comprises a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, any of the implementation manners in the embodiment one can be implemented.

[0039] Since the electronic device introduced in the embodiment is the device used for implementing the method in the embodiment one of the present application, the specific implementation manner of the electronic device in the embodiment and various forms of changes thereof can be understood by the person skilled in the art based on the method introduced in the embodiment one of the present application, and thus how the electronic device implements the method in the embodiment of the present application will not be described here in detail. As long as the device used for implementing the method in the embodiment of the present application is implemented by the person skilled in the art, it belongs to the scope of the present application.

[0040] Based on the same inventive concept, the present application provides the storage medium corresponding to the embodiment one, which is described in detail in the embodiment four. Embodiment

[0041] The embodiment provides a computer readable storage medium, which stores a computer program. When the computer program is executed by a processor, any of the implementation manners in the embodiment one can be implemented.

[0042] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can adopt a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program codes.

[0043] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flow or blocks Figure 1 one or more flow or blocks

[0044] These computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instructions which implement the function specified in the flowchart block or blocks. Figure 1 one or more flow or blocks Figure 1 one or more flow or blocks

[0045] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flow or blocks Figure 1 one or more flow or blocks

[0046] While the present application has been described with reference to specific implementations thereof, it should be understood that the specific implementations are merely illustrative of the general principles of the application and that the application is to be limited only by the scope of the claims.

Claims

1. A network reloading method for cross-border e-commerce browsers, characterized in that: Includes the following steps: Step 1: The cross-border e-commerce browser receives a server-side configuration file update notification, triggering a network reload process; Step 2: After receiving the server-side configuration file, the cross-border e-commerce browser parses it into a configuration object that the cross-border e-commerce browser can recognize. Step 3: Update the local configuration file of the cross-border e-commerce browser based on the configuration object, and generate a replacement configuration file; Step 4: Obtain an available port, create and run a new service instance based on the replaced configuration file, send a proxy request to the new service instance, and obtain the exit IP of the new service instance; Verify that the outgoing IP address matches the default IP address in the replacement configuration file. If they do not match, terminate the network reload and end the process. If they match, proceed to step 5. Step 5: Update the listening port in the local configuration file to the replacement configuration file, save the local configuration file, shut down the old service instance, set the new service instance as the global service instance, and complete the network reload. Step 6: After the network is reloaded, the latest configuration will take effect silently.

2. The network reloading method for a cross-border e-commerce browser according to claim 1, characterized in that: Step 1 specifically involves the cross-border e-commerce browser receiving a server-side configuration file update notification, triggering a network reload process, adding a mutex lock to the reload process to ensure thread safety, and pre-setting a lock release and global exception handling mechanism.

3. The network reloading method for a cross-border e-commerce browser according to claim 1, characterized in that: Step 2 specifically involves the following steps: After receiving the server-side configuration file, the cross-border e-commerce browser first decrypts it using a set decryption algorithm. Once decryption is successful, the decryption is resolved into a configuration object that the cross-border e-commerce browser can recognize. Simultaneously, asynchronous log upload logic is registered to upload network reload results.

4. A network reload method for a cross-border e-commerce browser according to claim 1, characterized in that: Step 4 specifically involves: obtaining an idle port, creating and running a new service instance based on the replacement configuration file, and pre-setting the rollback logic for the new service; after waiting for a set time, sending a proxy request to the new service instance to obtain the egress IP of the new service instance; Verify that the outgoing IP address matches the default IP address in the replacement configuration file. If they do not match, terminate the network reload and end the process. If they match, proceed to step 5.

5. A network reloading device for a cross-border e-commerce browser, characterized in that: include: The trigger process module: the cross-border e-commerce browser receives a server-side configuration file update notification and triggers the network reload process. The identification module parses the cross-border e-commerce browser into a configuration object that the browser can recognize after receiving the server-side configuration file. The replacement configuration file module updates the local configuration file of the cross-border e-commerce browser based on the configuration object and generates a replacement configuration file. The test module obtains an available port, creates and runs a new service instance based on the replaced configuration file, sends a proxy request to the new service instance, and obtains the exit IP of the new service instance. Verify that the outgoing IP address matches the preset IP address in the replacement configuration file. If they do not match, terminate the network reload and end the process. If they match, proceed to the update module. The update module updates the listening port in the local configuration file to the replacement configuration file, saves the local configuration file, shuts down the old service instance, sets the new service instance as a global service instance, and completes the network reload. The network reload module silently applies the latest configuration after network reload.

6. A network reloading device for a cross-border e-commerce browser according to claim 5, characterized in that: The triggering process module is as follows: the cross-border e-commerce browser receives a server-side configuration file update notification, triggers a network reload process, adds a mutex lock to the reload process to ensure thread safety, and presets a lock release and global exception capture mechanism.

7. A network reloading device for a cross-border e-commerce browser according to claim 5, characterized in that: The identification module specifically works as follows: After receiving the server-side configuration file, the cross-border e-commerce browser first decrypts it using a set decryption algorithm. After successful decryption, it parses the configuration file into a configuration object that the cross-border e-commerce browser can recognize. At the same time, it registers asynchronous log upload logic to upload network reload results.

8. A network reloading device for a cross-border e-commerce browser according to claim 5, characterized in that: The testing module specifically involves: obtaining an idle port, creating and running a new service instance based on the replacement configuration file, and pre-setting the new service rollback logic; after waiting for a set time, sending a proxy request to the new service instance to obtain the exit IP of the new service instance; verifying whether the exit IP is consistent with the pre-set IP in the replacement configuration file; if they are inconsistent, terminating the network reload and ending the step; if they are consistent, proceeding to the update module.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the method as described in any one of claims 1 to 4.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1 to 4.

Images