URL Rewriting with ExpressJS - url-rewriting
I would like to rewrite my URLs on my ExpressJS website. I've used this plugin, https://github.com/joehewitt/express-rewrite, but it doesn't work...
However, I might have made a mistake...
My app.js file :
var express = require('express')
, index = require('./routes/index.js')
, admin = require('./routes/admin.js')
, contact = require('./routes/contact.js')
, posts = require('./routes/posts.js')
, http = require('http')
, path = require('path')
, hash = require('./auth').hash
, db = require('./models')
, favicons = require('connect-favicons')
, rewriter = require('express-rewrite');
var app = express();
app.configure(function () {
app.set('port', process.env.PORT || 3000);
app.set('views', __dirname + '/views');
app.set('view engine', 'jade');
app.use(express.favicon(__dirname + '/public/images/FAVICON.ico'));
app.use(favicons(__dirname + '/public/images/apple-touch-icon.png'));
app.use(express.logger('dev'));
app.use(express.bodyParser());
app.use(express.static(path.join(__dirname, 'public')));
app.use(express.cookieParser());
app.use(express.cookieSession({
secret: 'SECRET',
cookie: { access: false }
})
);
app.use(rewriter);
app.use(app.router);
app.use(function(req, res, next){
res.render('404.jade', {
title: "404 - Page Not Found",
showFullNav: false,
status: 404,
url: req.url
});
});
});
app.configure('development', function () {
app.use(express.errorHandler());
});
app.get('/', index.index);
app.get('/toto', rewriter.rewrite('/heytoto'));
db.sequelize.sync().complete(function(err) {
if (err) {
throw err
} else {
http.createServer(app).listen(app.get('port'), function(){
console.log('Express server listening on port ' + app.get('port'))
})
}
});
My error message :
Express
500 TypeError: Object function app(req, res){ app.handle(req, res); } has no method 'match'
at Object.rewriter [as handle] (/Users/anthonycluse/Sites/Anthony-Cluse-Express/node_modules/express-rewrite/rewrite.js:3:26)
at next (/Users/anthonycluse/Sites/Anthony-Cluse-Express/node_modules/express/node_modules/connect/lib/proto.js:199:15)
at Object.cookieSession [as handle] (/Users/anthonycluse/Sites/Anthony-Cluse-Express/node_modules/express/node_modules/connect/lib/middleware/cookieSession.js:113:5)
at next (/Users/anthonycluse/Sites/Anthony-Cluse-Express/node_modules/express/node_modules/connect/lib/proto.js:199:15)
at Object.cookieParser [as handle] (/Users/anthonycluse/Sites/Anthony-Cluse-Express/node_modules/express/node_modules/connect/lib/middleware/cookieParser.js:60:5)
at next (/Users/anthonycluse/Sites/Anthony-Cluse-Express/node_modules/express/node_modules/connect/lib/proto.js:199:15)
at resume (/Users/anthonycluse/Sites/Anthony-Cluse-Express/node_modules/express/node_modules/connect/lib/middleware/static.js:60:7)
at SendStream.error (/Users/anthonycluse/Sites/Anthony-Cluse-Express/node_modules/express/node_modules/connect/lib/middleware/static.js:73:37)
at SendStream.EventEmitter.emit (events.js:126:20)
at SendStream.error (/Users/anthonycluse/Sites/Anthony-Cluse-Express/node_modules/express/node_modules/send/lib/send.js:147:51)
You could rewrite the URL before you get to the handler you want to use.
app.use(function(req, res, next) {
if (req.url === '/toto') {
req.url = '/heytoto';
}
next();
});
app.get('/heytoto', ...);
I've used a similar method to do URL rewrites with regular expressions.
So I had sort of the same issue. I wrote an app that uses the history API on browsers and I wanted to rewrite all non-static URLs back to index.html. So for static files I did:
app.configure(function() {
app.use('/', express.static(__dirname + '/'));
});
But then for the history API generated paths I did:
app.get('*', function(request, response, next) {
response.sendfile(__dirname + '/index.html');
});
This meant that any request that wasn't a file or directory in / (such as a URL generated by the history API) wouldn't be rewritten or redirected but instead the index.html file will be served and that then does all the JS routing magic.
Hopefully that's close to what you're looking for?
A solution that works without response.sendfile(..) is to use a rewrite middleware that is inserted prior to app.use(express.static(..)) like this:
// forward all requests to /s/* to /index.html
app.use(function(req, res, next) {
if (/\/s\/[^\/]+/.test(req.url)) {
req.url = '/index.html';
}
next();
});
// insert express.static(...)
This way, expressjs properly recognizes the rewrite. The static middleware will then take care of serving the file.
1) Your rewrite middleware must appear before the middleware/function that will handle the request.
Won't work:
app.use('/hello', () => sayHello() );
app.use(() => rewriteURLToHello()); //it's too late to try to rewrite a URL to /hello
Will work:
app.use(() => rewriteURLToHello()); //we can rewrite a URL to /hello
app.use('/hello', () => sayHello() ); //rewritten URL will be handled here
2) Your middleware must not be bound to the path you're trying to rewrite
Won't work:
app.use('/hello', (req, res, next) => {
//'/hello' has been trimmed from req.url
//req.url is / if the request was for /hello
req.url = '/goodbye'; //technically setting full path to /hello/goodbye
next(); //will only call other middleware in the /hello chain
});
app.use('/goodbye', () => sayBye()); //won't work
Will work:
app.use((req, res, next) => { //runs for every path. Same as .use('/',
//'/hello' has NOT been trimmed from req.url
//req.url is /hello if the request was for /hello
if (req.url.startsWith('/hello')) {
req.url = '/goodbye'; //full path now /goodbye
}
next(); //will continue calling all middleware
});
app.use('/goodbye', () => sayBye()); //will work
you could check the url with an if condition and use app.redirect to redirect to a certain url.
Try this:
app.get('/toto', function(req, res) {
res.redirect('/heytoto');
});
Related
Axios - Request header content-type was not present in the Access-Control-Allow-Headers list - ElasticSearch
I'm new to a lot of this technology, but I think I've diagnosed my issue and need some help. I've seen numerous posts on SO regarding this issue, but none have worked, though they have helped me diagnose issue. I believe the issue is when I send the Header Content-Type w/ my pre-flight w/ Axios, it fails. This is possibly due to lower/case upper case? The error has lower case, but I tried both on the server without luck. Basically, if I don't specify any header and Axios uses json as content-type, it works, but as soon as I specify Content-Type my pre-flight fails (even though I think post would work..). Here is the elasticsearch.yml cluster.name: "docker-cluster" network.host: 0.0.0.0 http.cors.enabled : true http.cors.allow-origin: "*" http.cors.allow-methods: OPTIONS,HEAD,GET,POST,PUT,DELETE http.cors.allow-headers: X-Requested-With,X-Auth-Token,Content-Type,Content-Length #http.cors.allow-credentials: true Here is my JS that I'm testing BTW w/ an Office Add-In solution in Visual Studio 2017 which I think is using IE as a browser. Main Func: var URL = "https://elasticsearch:9200/users/_search" const data = { "query": { "match": { "name": "freesoftwareservers" } } }; Do_Axios('get', URL, data, null, false) Do_Axios('post', URL, data, null, false) Do_Axios: async function Do_Axios(method, URL, data, headers, withCredentials) { return axios({ method: method, url: URL, withCredentials: withCredentials, //contentType: 'application/json', // does nothing //data: JSON.stringify(data), //Causes urlformencoded which is wrong data: data, //caues type to be json and I get error headers: { //"Content-Type": "application/json" }, }) .then(function (response) { console.log("Axios " + method + " response:"); console.log(response) return response; }) .catch(function (error) { console.log(error); }); } Note: I can get/post if I comment out //data but then the post doesn't run my query. If I uncomment data then Axios uses urlformencoded but that doesn't work. For now, I've been able to search API via urlformencoded queries, but I'd like to fix my ability to POST correctly to resolve future errors. I'm unsure if issue should be pointed to Axios or Elasticsearch if I open a request.
Well, I finally figured it out. I wonder how many of the other posts I read have similar issues... anyway, the issue was w/ my NGinX proxy server. No better way to learn about CORS then to setup an API and make CORS requests via IE! Without the below, I was still able to post w/ POSTMAN to the same URL which hit my nginx server, but the call from Axios/IE/JS Evironment failed. I found these snippets and this was the magic that needed added to my "regular" configuration: proxy_pass_header Access-Control-Allow-Origin; proxy_pass_header Access-Control-Allow-Methods; proxy_hide_header Access-Control-Allow-Headers; add_header Access-Control-Allow-Headers 'X-Requested-With, Content-Type'; add_header Access-Control-Allow-Credentials true; https://gist.github.com/sahilsk/b16cb51387847e6c3329 Here is my code as it stands, cleaned up but generic atm: Note: I pass axios because I can't figure out how to get my Webpack to transform/polyfill my funcs in seperate js files. But I can declare axios in the main func and pass it and then I can move my funcs into separate files as needed for organization. There is likely a better way to do without passing axios and configuring webpack Main Func: var username = "freesoftwareservers" var ipv4 = "192.168.1.255" var showhelp = "false" await Do_AddUserToES(axios,username, ipv4, showhelp) Get_UserFromES(axios,username) var index = "users" var query = { query: { match: { "username": username } } }; Get_PostQueryToES(axios,query, index) Funcs: function Do_Axios(axios, method, URL, data, headers, withCredentials) { return axios({ method: method, url: URL, withCredentials: withCredentials, data: data, headers: headers, }) .then(function (response) { console.log("Axios " + method + " response:"); console.log(response) return response; }) .catch(function (error) { console.log(error); }); } function Get_ESURL(Bool_Search, Bool_Doc, Bool_Update, Opt_Index, Opt_IndexKey) { var ESUrl = "https://elasticsearch:9200" var ESSearch = "/_search" var ESDoc = "/_doc" var ESUpdate = "/_update" var ReturnURL = ESUrl if (Opt_Index != undefined) { ReturnURL = ReturnURL + "/" + Opt_Index } if (Bool_Search == true) { ReturnURL = ReturnURL + ESSearch } if (Bool_Doc == true) { ReturnURL = ReturnURL + ESDoc } if (Bool_Update == true) { ReturnURL = ReturnURL + ESUpdate } if (Opt_IndexKey != undefined) { ReturnURL = ReturnURL + "/" + Opt_IndexKey } console.log("ReturnURL:" + ReturnURL) return ReturnURL; } function Do_AddUserToES(axios, username, ipv4, showhelp) { var adduser = { "username": username, "ipv4": ipv4, "showhelp": showhelp }; var URL = Get_ESURL(false, true, false, "users", username) return Do_Axios(axios, 'post', URL, adduser, null, false); } function Get_UserFromES(axios, username) { var URL = Get_ESURL(false, true, false, "users", username) return Do_Axios(axios, 'get', URL, null, null, false); } function Get_PostQueryToES(axios, query, index) { var URL = Get_ESURL(true, false, false, index) return Do_Axios(axios, 'post', URL, query, null, false); }
Sails - Access Controller function(req,res) from Service
I have a Controller method: DbController.create to create database entries. This is the following format: create: function (req, res) { var params = req.body; Db.create({ ... There is a route for this Controller method: 'POST /createData': 'DbController.create' I can use CURL to this URL with no problems (curl -X POST --data 'userId="testuser1"' http://localhost:1337/createData), and from my UI code I can call this using sails-io.js and io.socket.post(....). The problem is that I want to use this from my Service now (DbService). I'm not sure how I can go about this, because simply using DbController.create requires a req and res parameter to be passed, but all I have is the data/params/body. Thanks
The best way would be to move the create logic in some service method so that it can be used from anywhere in project. Once this is done, then invoke that method with necessary parameters from DbController.create as well as from some other service. Sample: // DBService: createData: (params, callback) => { Db.create(params)... } // DBController: create: (req, res) => { const params = req.body; DBService.createData(params, (err, results) => { if (err) { return res.serverError(err); } return res.json(results); }); } // SomeOtherService: someMethod: (params, callback) => { DBService.createData(params, callback); } Another way (which will unnecessary make http request) is to make a HTTP call from service to the API endpoint of DbController.create from the service.
How to Redirect POST Request to another Route in Nodejs
I have a nodejs server application that provides an API to a client-side application. Previously, the app will send an AJAX request that contains an action parameter in the request object, req.body.action, to the main route (i mean '/') to proceed an action base on this parameter. However, I need to change/redirect the route of any AJAX POST request from the main route, '/', to action specific route, '/{action route}'. N.B.: I want to allow backward compatibility for every user that hasn't updated the client side app to take this change in consideration. i.e, can't modify the AJAX request code for those users. I have tried this code below but it does not work. app.use(bodyParser.json() ); app.post('/', function(req, res){ if( (req.body.action) && (req.body.action === 'action-1')){ res.redirect(307, '/action-1'); } if( (req.body.action) && (req.body.action === 'action-2')){ res.redirect(307, '/action-2'); } }); app.post("/action-1", function (req, res) { //would have proceeded the request for action-1 here but it's not routed }); app.post("/action-2", function (req, res) { //would have proceeded the request for action02 here but it's not routed });
You can try this way: app.use(bodyParser.json() ); app.post('/', function(req, res){ if( (req.body.action) && (req.body.action === 'action-1')){ return routes.act1(req, res); } if( (req.body.action) && (req.body.action === 'action-2')){ return routes.act2(req, res); } }); app.post("/action-1", routes.act1); app.post("/action-2", routes.act2); it's not redirect, but works.
Parse express server side login using express-session
I'm using parse on node. I have an express app, and a JS browser app, that is hosted off the express server. At the moment the app has it's own login. It logs the user in on the client, and the client remains logged in. I want to be able to log the client in via an express route /login. When they log in via this route, i want to log them in on the client side. I have poured over documentation on this but I have struggled to find any real examples of how this is all done. Here is some code i have found: var cookieSession = require('cookie-session'), // I added this require as it seems the code is using it; session = require('express-session'); app.use(cookieSession({ name: COOKIE_NAME, secret: "SECRET_SIGNING_KEY", maxAge: 15724800000 })); // // This will add req.user if they are logged in; // app.use(function (req, res, next) { Parse.Cloud.httpRequest({ url: 'http://localhost:1337/parse/users/me', headers: { 'X-Parse-Application-Id': 'myAppId', 'X-Parse-REST-API-Key': 'myRestAPIKey', 'X-Parse-Session-Token': req.session.token } }).then(function (userData) { req.user = Parse.Object.fromJSON(userData.data); next(); }).then(null, function () { return res.redirect('/login'); }); }); // // login route; // app.post('/login', function(req, res) { Parse.User.logIn(req.body.username, req.body.password).then(function(user) { req.session.user = user; req.session.token = user.getSessionToken(); res.redirect('/'); }, function(error) { req.session = null; res.render('login', { flash: error.message }); }); }); // // and logout. // app.post('/logout', function(req, res) { req.session = null; res.redirect('/'); }); This looks pretty good, but this won't add a session on the client? How do parse the server login down to the client; Do i pass the session Token and use it on the client? // // If i call this code in the browser, i want the logged in user; // var current_user = Parse.User.current(); I have been unable to find any real code on-line that demonstrates all of this in the best-practice manner. Is this the 'best practice' known solution or is there a better way of doing this?
How do I set Meteor to not cache anything for a specific page?
I am working on a project where I am using Meteor as an implementation. There are set of pages that are being cached and there's no concern. However, there is one page in the project that I am trying to set for no-cache. How do I achieve that? EDITED: Based on chosen accepted answer; I achieved the desired result with this wrapping code: if (Meteor.isServer) { Meteor.startup(function () { WebApp.rawConnectHandlers.use(function (req, res, next) { res.setHeader('cache-control', 'no-cache'); res.setHeader('expires', '0'); res.setHeader('Content-Type', 'text/html'); res.setHeader('charset', 'utf-8'); next(); }); }); }
You can use WebApp to configure cache headers: //Server code WebApp.rawConnectHandlers.use('/noCachePagePath', function(req, res, next) { res.setHeader('cache-control', 'no-cache'); next(); });