Skip to main content

expressJS

  const app = express();

/**
* Changes made to enable CORS
*/

const allowCrossDomain = (req, res, next) => {
    res.header('Access-Control-Allow-Origin', '*');
    res.header('Access-Control-Allow-Methods', 'GET,PUT,POST,DELETE');
    res.header('Access-Control-Allow-Headers', 'Content-Type, Authorization, token');

    // intercept OPTIONS method
    if ('OPTIONS' == req.method) {
        res.sendStatus(200);
    }
    else {
        next();
    }
};

//Allow cross domain.
app.use(allowCrossDomain);

Comments

Post a Comment

Popular posts from this blog

Kubernetes

What is Kubernetes? Kubernetes is a portable, extensible, open-source platform for managing containerized workloads and services, that facilitates both declarative configuration and automation. It has a large, rapidly growing ecosystem.  The name Kubernetes originates from Greek, meaning helmsman or pilot. Google open-sourced the Kubernetes project in 2014. Kubernetes combines over 15 years of Google’s experience running production workloads at scale with best-of-breed ideas and practices from the community. Why you need Kubernetes and what it can do? Containers are a good way to bundle and run your applications. In a production environment, you need to manage the containers that run the applications and ensure that there is no downtime. For example, if a container goes down, another container needs to start. Wouldn’t it be easier if this behavior was handled by a system? That’s how Kubernetes comes to the rescue! Kubernetes provides you with a framework to run distributed systems ...

11 - JPA/Hibernate Interview Questions

Why Hibernate? Answer : In Short it helps you solve some problem which indirectly comes when you are using JDBC 1. Help you to avoid lots of boilerplate code. 2. Helps you to avoid doing any Connection Management and Transaction Management explicitly. 3. Helps you DB Developer to do exciting things rather than helping the Junior or Mid Level engineer for writing native query. 4. It creates two way data binding between your table and POJO i.e. any change in POJOs's reflects in db table and any changes in db table reflects in application POJO, i.e. objectifies the data layer. 5. Future Proof : Very minimal effort needed to migrate the one database type to another. 6. When you want to do lot of business operation on your POJO's, and you want those POJO's to be handy. When Not to use Hibernate? Answer : Few points to be seen before introducing the Hibernate into your application 1. If you do not have Persistence Layer, there is no use of Hibernate. 2. Legacy ...