When publishing the website in Liferay, it’s good practice to restrict access to admin urls outside the LAN. you can block the access to urls by adding the rewrite rules on the web-server. In my case, I am using the apache webserver and following are apache configurations for the same. httpd.conf
Tag Archives: Web Server
Dynamo is a minimal, Swift implementation of a Web server supporting SSL that can also be used in Objective-C applications. Dynamic content can be provided in what you could call “swiftlets” which are dynamically loadable bundles in your document root. These bundles hot-swap when modified using method Swizzling so the server does not have to be restarted.
For further information about the classes and protools that make up Dynamo you consult the jazzy docs here.
In this example we will discuss Apache Tomcat Servlet/JSP container’s clustering and session replication related configurations. Apache Tomcat server is lightweight server that is relatively easy to set-up. It has many features that enable high flexibility. Tomcat can be fine-tuned to do well for some traffic, but if your traffic is expected to be large you may need to distribute the traffic over several Tomcat instances that we will refer to as workers sometimes. Thus you may want to set-up a cluster of Tomcat instances.
Apache Tomcat 8 Configuration Reference
Clustering/Session Replication HOW-TO
Load Balancer HOW-TO
Tomcat Clustering – A Step By Step Guide
An Introduction To Tomcat Cluster Configuration
Apache Tomcat mod_jk Connector Configuration Made Simple
Apache Tribes – Introduction
The Cluster Valve object
The Apache Tomcat Connector – Generic HowTo
The Apache Tomcat Connector
Working with mod_jk
The Apache Tomcat Connector – Webserver HowTo
The Apache Tomcat Connector – Reference Guide
An In-Depth Look at Tomcat’s Clustering Mechanisms
Netty is used today in all kinds of applications, all over the Internet, to handle thousands (if not millions) of chat conversations, multiplayer games including Minecraft, Twitter, and many other applications. However, it hasn’t made it very far into the mindshare of enterprise programmers developing business applications.
I believe that Netty can introduce a new wave of functionality that other solutions simply cannot match because of its fully bi-directional text and binary non-HTTP data transport, along with its support for many more concurrent clients than traditional “thread-per-socket” servers.
You may know about Netty’s prowess with WebSockets, but did you know it can function extremely well as a traditional web server? Due to its very thoughtful design, by adding appropriate handlers to its pipeline, Netty can handle virtually any traffic. It can also handle multiple types concurrently, such as WebSockets and HTTP over the same port at the same time. By combining these together, programmers are spared from dealing with nuisances such as CORS (Cross Origin Resource Sharing) that can rear their ugly head when a browser tries to make requests to servers it did not download from.
Table of Contents
- Hardware Requirements
- Supported Web Browsers
- Quick Start
- Data Store
- Deploy to a subdirectory (relative url root)
- Putting it all together
- OmniAuth Integration
- External Issue Trackers
- Mapping host user and group
- Available Configuration Parameters
- Rake Tasks