blocks|key|2338357|text|只将子域(api.example.com)指向您的api服务器是绝对可能的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2338358|DNS不控制子目录，因此example.com/api的DNS条目将无效|offset|length|style|CODE|2338359|如果您的服务器有一个IP地址，则需要添加值为：api.example.com的A记录。|2338360|如果您的服务器有域名，则需要创建一个CNAME记录。|2338361|entityMap^0|0|C|F|0|N|F|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@$D|S|E|T|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|M|$]]

It will definitely be possible to point just the subdomain (api.example.com) to your api server.

DNS doesn't control subdirectories so a DNS entry of <code>example.com/api</code> would be invalid

If you have an IP address for your server you will need to add an A record with the value: <code>api.example.com</code>.

If you have a domain name for your server you will need to create a CNAME record.

blocks|key|2338398|text|建议您使用nginx和单独的api服务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2338399|但由于某些原因，你无法避免它(或者你不想要它，因为你只是想尽快向客户展示原型)。|2338400|您可以编写中间件来从报头捕获主机并将其转发到某个自定义路由器：|2338401|1)+/middlewares/forwardForSubdomain.js|offset|length|style|CODE|2338402|module.exports+=+
++++(subdomainHosts,+customRouter)+=>+{
++++++return+(req,+res,+next)+=>+{
++++++++let+host+=+req.headers.host+?+req.headers.host+:+'';+//+requested+hostname+is+provided+in+headers
++++++++host+=+host.split(':')[0];+//+removing+port+part

++++++++//+checks+if+requested+host+exist+in+array+of+custom+hostnames
++++++++const+isSubdomain+=+(host+&&+subdomainHosts.includes(host));
++++++++if+(isSubdomain)+{+//+yes,+requested+host+exists+in+provided+host+list
++++++++++//+call+router+and+return+to+avoid+calling+next+below
++++++++++//+yes,+router+is+middleware+and+can+be+called
++++++++++return+customRouter(req,+res,+next);+
++++++++}

++++++++//+default+behavior
++++++++next();
++++++}
++++};|code-block|syntax|javascript|2338403|2)以api路由器为例/routers/apiRouter.js|2338404|const+express+=+require('express');
const+router+=+express.Router();

router.get('/users',+(req,+res)+=>+{
++//+some+operations+here
});

module.exports+=+router;|2338405|3)在/处理程序之前附加中间件：|2338406|const+path+=+require('path'),
++++++http+=+require('http'),
++++++https+=+require('https'),
++++++helmet+=+require('helmet'),
++++++express+=+require('express'),
++++++app+=+express();

const+mainRouter+=+require('./routers/mainRouter');

//+security+improvements
app.use(helmet());

//+ATTACH+BEFORE+ROUTING
const+forwardForSubdomain+=+require('./middlewares/forwardForSubdomain');
const+apiRouter+=+require('./routers/apiRouter');
app.use(
++forwardForSubdomain(
++++[
++++++'api.example.com',
++++++'api.something.com'
++++],
++++apiRouter
++)
);

//+main+pages
app.use('/',+mainRouter);

//+route+the+public+directory
app.use(express.static('public'));

//+404s
app.use((req,+res)+=>+{
++++res.status(404).sendFile(path.join(__dirname,+"views/404.html"));
})|2338407|附注:它的功能与express-vhost包中的look+at+the+code相同|2338408|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/doanythingfordethklok/express-vhost|1|https://raw.githubusercontent.com/doanythingfordethklok/express-vhost/master/lib/vhost.js^0|0|0|0|3|Z|0|0|B|L|0|0|3|1|0|0|8|D|0|O|G|1|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1C|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1D|8|@$H|1E|I|1F|J|K]]|9|@]|A|$]]|$1|L|3|M|5|N|7|1G|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|1H|8|@$H|1I|I|1J|J|K]]|9|@]|A|$]]|$1|S|3|T|5|N|7|1K|8|@]|9|@]|A|$O|P]]|$1|U|3|V|5|6|7|1L|8|@$H|1M|I|1N|J|K]]|9|@]|A|$]]|$1|W|3|X|5|N|7|1O|8|@]|9|@]|A|$O|P]]|$1|Y|3|Z|5|6|7|1P|8|@]|9|@$H|1Q|I|1R|1|1S]|$H|1T|I|1U|1|1V]]|A|$]]|$1|10|3|-4|5|6|7|1W|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]|18|$5|13|14|15|A|$16|19]]]]

I recommend You to use nginx and separate api service.

But because of some reasons You cannot avoid it (or You don't want it, cause You just want show prototype to customer ASAP).

You can write middleware that will catch host from header and forward to some custom router:

1) <code>/middlewares/forwardForSubdomain.js</code>:

<pre><code>module.exports = 
 (subdomainHosts, customRouter) =&gt; {
 return (req, res, next) =&gt; {
 let host = req.headers.host ? req.headers.host : ''; // requested hostname is provided in headers
 host = host.split(':')[0]; // removing port part

 // checks if requested host exist in array of custom hostnames
 const isSubdomain = (host &amp;&amp; subdomainHosts.includes(host));
 if (isSubdomain) { // yes, requested host exists in provided host list
 // call router and return to avoid calling next below
 // yes, router is middleware and can be called
 return customRouter(req, res, next); 
 }

 // default behavior
 next();
 }
 };
</code></pre>

2) api router as an example <code>/routers/apiRouter.js</code>:

<pre><code>const express = require('express');
const router = express.Router();

router.get('/users', (req, res) =&gt; {
 // some operations here
});

module.exports = router;
</code></pre>

3) attach middleware before <code>/</code> handler: 

<pre><code>const path = require('path'),
 http = require('http'),
 https = require('https'),
 helmet = require('helmet'),
 express = require('express'),
 app = express();

const mainRouter = require('./routers/mainRouter');

// security improvements
app.use(helmet());

// ATTACH BEFORE ROUTING
const forwardForSubdomain = require('./middlewares/forwardForSubdomain');
const apiRouter = require('./routers/apiRouter');
app.use(
 forwardForSubdomain(
 [
 'api.example.com',
 'api.something.com'
 ],
 apiRouter
 )
);

// main pages
app.use('/', mainRouter);

// route the public directory
app.use(express.static('public'));

// 404s
app.use((req, res) =&gt; {
 res.status(404).sendFile(path.join(__dirname, "views/404.html"));
})
</code></pre>

P.S. It does the same that in <a href="https://github.com/doanythingfordethklok/express-vhost" rel="noreferrer">express-vhost</a> package, <a href="https://raw.githubusercontent.com/doanythingfordethklok/express-vhost/master/lib/vhost.js" rel="noreferrer">look at the code</a>

I've been Googling for some time, but can't find any useful answers. I'm trying to get a subdomain for an api on my website <code>api.example.com</code>. However, all answers said that I needed to change my DNS to redirect <code>api.example.com</code> to <code>example.com/api</code>, which I don't want. Is it possible to just serve <code>api.</code> instead of redirect to <code>/api</code>? How would I go about doing that?

<ol>
<li>I'm using express.</li>
<li>I don't want to use any other packages that aren't built-in.</li>
</ol>

<pre class="lang-js prettyprint-override"><code>const path = require('path'),
 http = require('http'),
 https = require('https'),
 helmet = require('helmet'),
 express = require('express'),
 app = express();

const mainRouter = require('./routers/mainRouter.js');

// security improvements
app.use(helmet());

// main pages
app.use('/', mainRouter);

// route the public directory
app.use(express.static('public'));

app.use(/* API subdomain router... */)

// 404s
app.use((req, res) =&gt; {
 res.status(404).sendFile(path.join(__dirname, "views/404.html"));
})
</code></pre>

Subdomain (host) based routing in Express

中间件

服务器

路由器

路由

我已经用谷歌搜索了一段时间，但是找不到任何有用的答案。我正在尝试在我的网站api.example.com上获得一个应用编程接口的子域。然而，所有的回答都说我需要更改我的域名系统，将api.example.com重定向到example.com/api，这是我不想要的。有没有可能不重定向到/api而只服务于api.？我该怎...

问Express中基于子域(主机)的路由
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Express中基于子域(主机)的路由EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Express中基于子域(主机)的路由
EN