GoEdge It is a tool that can help you quickly build a CDN & WAF platform. It supports HTTP, HTTPS, Websocket, TCP, TLS, UDP, PROXY Protocol, IPv6, WAF and other features, and supports multiple third-party DNS services.

The v0.5.3 version mainly improves the cache LFU algorithm, Chinese domain name, UDP, anti-leech, and automation.


  • Detail optimization
    • When the API node starts, the page prompts “API node is starting, please wait patiently for completion” to let users know what is happening
    • Added edge-admin upgrade commandused to upgrade the management system online
    • Even after the node is offline, it still displays the version, main program location and other information in the running state
    • Whether to add a remote start option to the clusterwhich can be set in the basic cluster settings – more options, and is enabled by default; after it is enabled, when the node is offline, it will automatically try to remotely start the edge-node process through SSH
    • Display the node installation file download link on the node manual installation page
    • Add anti-leech functionwhich can only be set in WAF in the past, but can also be used directly in the service settings
    • The certificate request task no longer distinguishes between administrators, that is, a certificate request task created by one administrator can also be run by another administrator.
    • BugFix: Fix the problem of reading the bandwidth error of the previous month
  • automation
    • Added automatic clock synchronization option to the clusterwhich can be set in Cluster Basic Settings – More Options, enabled by default
    • The cluster adds the option to automatically install nftableswhich can be set in the cluster basic settings – more options, and is not enabled by default; this option can also be selected when creating a cluster
    • When modifying the time zone in the management interface settings, it will also be applied to the API node, that is, the API node log and other related date formatting will follow the time zone setting of the management interface.
    • When creating a node, try to automatically read the IP from the node name, now you can only fill in one name, as long as the IP is included, you can go directly to the next step
  • domain name
    • Chinese and capital letters can be used in domain names and record names
    • The Add Domain Name window prompts you to add a generic domain name
    • Add the option “Only allow bound domain name access” when creating a cluster
    • Health check to check whether the domain name exists when setting the domain name
  • access log
    • Display Chinese domain names in the form of tags in the access log
    • Add the origin status code to the access log
    • Added unified service settings to cluster settings, including domain name and log related configuration; now you can set not to record service error log to node running log
    • Added “Ignore URI Parameters” option for caching conditions
  • DNS
    • You can set the default TTL of DNS records when creating a cluster
    • Added EdgeDNS API for domain name resolutionyou can connect to the smart DNS service provided by other GoEdge systems through API
    • DNS domain name adds paging, which can be viewed in Domain Name Resolution–Single Service Provider Account
    • Cluster Settings–DNS Settings page displays DNS account name
  • cache
    • Each cache condition supports 206 Partial Content by default
    • Added “Ignore URI Parameters” option for caching conditions


  • At startup, try to automatically set the binlog expiration time, binlog cache and other related parameters
  • Optimize interface permissions, some interfaces do not allow ordinary users (note: non-admin users) to be called through REST
  • The client side refreshes the warm-up cache for more than 5 minutes and automatically considers it to be completed.
  • BugFix: Fixed the problem that DNSPod could only retrieve the first 100 domain names
  • It is no longer mandatory to repair node problems when synchronizing domain name resolution
  • When the received content of the REST interface is empty, the default is {}
  • The service traffic interface is added 5 minutes to the query interface
  • Use concurrent queues to install and upgrade data tables to avoid taking too long to install or upgrade
  • BugFix: Fix the problem of uneven distribution of multiple log database nodes
  • Automatically adjust the number of write access logs written to a single database transaction


  • Improve cache LFU algorithmnow if the size of the cache file reaches the capacity limit, the expired cache will be cleared first, and then the old cache will be cleared;Fixed the bug of deleting hot files by mistake in the past
  • You can use the EdgeRecover environment variable to instruct the database to recover, and use env EdgeREcover=on edge-node start when starting
  • When the access log cannot be submitted to the API node due to its large size, the requestBody will be automatically removed and then try again to improve the success rate of access log records.
  • BugFix: Fixed an issue where UDP messages may not be forwarded correctly when there are multiple network exits
  • Ignore IP whitelist and LAN connections when checking synflood
  • Websocket also supports automatic retry on failure
  • Websocket supports custom response Header
  • BugFix: Fixed the bug that RPC options did not take effect, and now options such as compression and maximum message size can also be used during HTTP transmission
  • The service configuration is initialized only once, preventing conflicts when the configuration changes
  • Some page texts support traditional Chinese (original)
  • IP list supports regular cleaning
  • Deleted IPs are no longer written to the local database
  • Optimize service-related error message prompts to avoid trouble caused by too many error prompts

Full change description:https://goedge.cn/docs/Releases/Index.md

#GoEdge #CDN #v053 #released #improved #cache #LFU #algorithm #UDP #antileech #News Fast Delivery

Leave a Comment

Your email address will not be published. Required fields are marked *