Using HTTP output compression
Posted: Mon Nov 04, 2013 2:18 pm
A basic way to improve the performance of HTTP applications is to make sure you have HTTP output compression turned on.
For RPG LongRange users this would normally be turned on by default.
For LANSA LongRange users it depends on how you have configured your IIS (Windows) or Apache (IBM i) HTTP web server.
This article discusses how to do this for V5R3 on an IBM i server (the approach would be very similar for all IBM i versions of Apache):
http://publib.boulder.ibm.com/infocente ... cmprsn.htm
This boils down to configuring your Apache web server instance to compress certain types of files before sending them to the client:
By using Fiddler ( http://fiddler2.com/ ) and your PC’s web browser it is fairly easy to see whether your HTTP server is compressing output data.
You can also use Fiddler to inspect HTTP requests coming from iPad or iPhone. See http://fiddler2.com/documentation/Confi ... gureForiOS
For RPG LongRange users this would normally be turned on by default.
For LANSA LongRange users it depends on how you have configured your IIS (Windows) or Apache (IBM i) HTTP web server.
This article discusses how to do this for V5R3 on an IBM i server (the approach would be very similar for all IBM i versions of Apache):
http://publib.boulder.ibm.com/infocente ... cmprsn.htm
This boils down to configuring your Apache web server instance to compress certain types of files before sending them to the client:
- Image1.png (72.36 KiB) Viewed 3894 times
You can also use Fiddler to inspect HTTP requests coming from iPad or iPhone. See http://fiddler2.com/documentation/Confi ... gureForiOS