Over a million developers have joined DZone.

Node.js Quickie: Checking the Current Domain Name

DZone's Guide to

Node.js Quickie: Checking the Current Domain Name

· Web Dev Zone ·
Free Resource

Bugsnag monitors application stability, so you can make data-driven decisions on whether you should be building new features, or fixing bugs. Learn more.

I'm working on a quick proof of concept (for a killer idea, honest, I swear) that needs to rely on a subdomain name to determine how the application responds. So, as an example, I want to see something different for foo.app.com versus goo.app.com, and obviously support www.app.com and app.com. Here is a quick way to handle that.

First, my thanks to StackOverflow user cjohn for his answer. If you examine the Request object in your Node app you can introspect the headers object to view the host value.

I did a quick dump (JSON.stringify(req.headers)) to see what this looked like:

Pretty much what I expected. So I wrote a quick little snippet that would focus on returning just the subdomain:

function getSubdomain(h) {
  var parts = h.split(".");
	if(parts.length == 2) return "www";
	return parts[0];

//later on...
exports.index = function(req, res) {
  var subdomain = getSubdomain(req.headers.host);
  res.render('index', { title: 'Express', subdomain:subdomain });

You can see both the function as well as the route that makes use of it. This isn't perfect. If a user hits the site via x.y.app.com then you (probably) want to see x.y as a result, but for my needs I'm fine with just x being returned.

Monitor application stability with Bugsnag to decide if your engineering team should be building new features on your roadmap or fixing bugs to stabilize your application.Try it free.


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}