Hosterra/domain-forward
Hosterra/domain-forward
1
1
Fork 0
Code Issues Pull requests Releases 1 Activity

Fix import, README update

Browse source
This commit is contained in:
Wildan M 2023-04-24 08:17:25 +07:00
commit 4acae4608a
3 changed files with 13 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

5
CHANGES.md
View file

@ -1,5 +1,10 @@
# CHANGES # CHANGES
## v2.5 (2023-04-24)
+ Add `http-status` TXT record option to set HTTP status code. Contributed by [@dzegarra](https://github.com/willnode/forward-domain/pull/4)
+ Improve lock mechanism when a website is verificating certs.
## v2.4 (2023-04-21) ## v2.4 (2023-04-21)
+ Fix global service lock when a website is verificating certs. + Fix global service lock when a website is verificating certs.

14
README.md
View file

@ -7,12 +7,12 @@
> We're back with improvements! See [CHANGES.md](CHANGES.md) > We're back with improvements! See [CHANGES.md](CHANGES.md)
This service forwards domains using 301 HTTP(s) redirects by default. This service forwards domains using HTTP(s) redirects.
Possible scenarios: Example scenarios:
+ Forward non-www to www URLs or inversely + Forward non-www to www domains or vice versa
+ Forward old URLs to new URLs + Forward old domains to new domains
Why using this service? Why using this service?
@ -22,7 +22,7 @@ Why using this service?
+ Completely anonymous + Completely anonymous
+ Completely free + Completely free
How it is possible? How does it works?
+ Point your domain to us using CNAME or A/AAAA records + Point your domain to us using CNAME or A/AAAA records
+ Tell us where to forward using TXT records + Tell us where to forward using TXT records
@ -47,7 +47,7 @@ _.old.com IN TXT forward-domain=https://new.net/*
The star `*` at the end tells us that the remaining URL path is also forwarded to the destination URL. The star `*` at the end tells us that the remaining URL path is also forwarded to the destination URL.
> If you use Cloudflare or any DNS which supports [CNAME Flattening](https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/), you still can use CNAME records pointing to `r.forwarddomain.net`, it's much recommended to use CNAME records rather than A/AAAA records. > If you use Cloudflare or any DNS which supports [CNAME Flattening](https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/), you still can use CNAME records pointing to `r.forwarddomain.net`. It's recommended to use CNAME records rather than A/AAAA records.
You can choose the type of redirection you want to use by declaring the `http-status` value: You can choose the type of redirection you want to use by declaring the `http-status` value:
@ -56,7 +56,7 @@ www.old.com IN CNAME r.forwarddomain.net
_.www.old.com IN TXT http-status=302;forward-domain=https://old.com/* _.www.old.com IN TXT http-status=302;forward-domain=https://old.com/*
``` ```
> Only the http status code 301 and 302 are supported. > Only the HTTP status code 301 and 302 are supported. By default it's 301, which is permanent redirection. Set to 302 if you want temporary redirection, it has effect on search engine indexing.
## FAQ ## FAQ

2
stat.js
View file

@ -1,7 +1,7 @@
import { config } from "dotenv"; import { config } from "dotenv";
import { execSync } from "child_process"; import { execSync } from "child_process";
import http from "http"; import http from "http";
import { isMainProcess } from "./src/util"; import { isMainProcess } from "./src/util.js";
const updateStat = function () { const updateStat = function () {
// run npm stat // run npm stat