A Yeoman generator for Express.js based 12-factor apps and apis using Typescript
This generator scaffolds a fully functioning REST API server complete with interactive documentation, API validation, structured logging, environment driven config, and more. Simply run the generator and smile 😀
This document defines a “problem detail” as a way to carry machine- readable details of errors in a HTTP response, to avoid the need to invent new error response formats for HTTP APIs.
Pushing Nginx to its limit with Lua – CloudFlare blog
Nginx+Lua is a self-contained web server embedding the scripting language Lua. Powerful applications can be written directly inside Nginx without using cgi, fastcgi, or uwsgi. By adding a little Lua code to an existing Nginx configuration file, it is easy to add small features.
Tengine is a web server originated by Taobao, the largest e-commerce website in Asia. It is based on the popular Nginx HTTP server and has many advanced features. Tengine has been proven very stable and efficient on the top 100 websites, including taobao.com and tmall.com.
Visitor Tracking Without Cookies (or How To Abuse HTTP 301s) | Scatmania
To illustrate one of the ambiguities in the law, I’ve implemented a tool which tracks site visitors almost as effectively as cookies (or similar technologies such as Flash Objects or Local Storage), but which must necessarily fall into one of the larger grey areas. My tool abuses the way that “permanent” (301) HTTP redirects are cached by web browsers.
The Mongrel2 Web Server Project
Mongrel2 is an application, language, and network architecture agnostic web server that focuses on web applications using modern browser technologies
Mock Your Ajax Requests with Mockjax for Rapid Development
The mockjax plugin is a development and testing tool for intercepting and simulating ajax requests made with jQuery with a minimal impact on changes to production code.
This is a sweet piece of Javascript that allows to build frontends on simply configured mock ajax data, speeding up the production pipeline on web projects.
Fast Web Performance Starts with DNS
A web page is an ecosystem where multiple objects contribute to the web page content, and as a result to its slowness or even unavailability. Some of the slowness can be due to poor server performance but at times is due to DNS related issues.
PHProxy | Download PHProxy software for free at SourceForge.net
PHProxy is a web HTTP proxy programmed in PHP meant to bypass firewalls and access otherwise inaccessible resources (i.e. blocked websites). If the server this script is run on can access a resource, so can you!
lcamtuf’s blog: HTTP cookies, or how not to design protocols
For as long as I remember, HTTP cookies have been vilified as a grave threat to the privacy of online browsing; wrongly so. That said, the mechanism itself is a very interesting cautionary tale for security engineers – and that will be the theme of today’s feature.
URL Design is a complex subject. I can’t say there are any “right” solutions — it’s much like the rest of design. There’s good URL design, there’s bad URL design, and there’s everything in between — it’s subjective.
Ben Strong’s Blog: Google and Microsoft Cheat on Slow-Start. Should You?
to match Google’s page load times you have to cheat on the tcp slow-start algorithm. It appears that stretching the parameters a little bit is fairly common, but Google and Microsoft push it a lot further than most.
evercookie – virtually irrevocable persistent cookies
evercookie is a javascript API available that produces extremely persistent cookies in a browser. Its goal is to identify a client even after they’ve removed standard cookies, Flash cookies (Local Shared Objects or LSOs), and others. evercookie accomplishes this by storing the cookie data in several types of storage mechanisms that are available on the local browser. Additionally, if evercookie has found the user has removed any of the types of cookies in question, it recreates them using each mechanism available.
maccman’s juggernaut at master – GitHub
Juggernaut lets you push data to browser, which means you can do awesome things like multiplayer gaming, chat, realtime collaboration and more! Juggernaut is super simple and easy to get going.
* node.js server
* Ruby client
* Supports the following protocols:
* WebSocket
* Adobe Flash Socket
* ActiveX HTMLFile (IE)
* Server-Sent Events (Opera)
* XHR with multipart encoding
* XHR with long-polling
* Reconnection support
Clean URIs are one component of a clean website, and it is an important one. The majority of end-user access to the Internet involves a URI, and whether or not the user actually enters the URI, they are working with one nonetheless.
WebTest has an easy syntax with steps having meaningful names that can be understood even when you don’t know WebTest. Additionally, the recorder allows you to quickly generate a first draft of your tests that you can adapt and refactor to build robust tests suites. Don’t forget: capture/replay is the least cost-effective way of automating test cases!
kanaka’s noVNC at master – GitHub
noVNC is a VNC client implemented using HTML5 technologies, specifically Canvas and WebSocket (supports ‘wss://’ encryption).
For browsers that do not have builtin WebSocket support, the project includes web-socket-js, a WebSocket emulator using Adobe Flash .
In addition, as3crypto has been added to web-socket-js to implement WebSocket SSL/TLS encryption, i.e. the “wss://” URI scheme.
You can use any of the Stomp Clients to work with any JMS compliant message broker, for example HornetQ. There are Stomp clients for many languages, and Stomple adds JavaScript via WebSockets. This means that you can send and receive JMS messages directly in the browser (when it supports WebSockets).
A HTTP Proxy Server in 20 Lines of node.js Code
Yes. Node.js is very cool indeed.
EricLaw’s IEInternals : COMET Streaming in Internet Explorer
One challenge with using XMLHTTPRequest is that browsers behave differently when it comes to streaming of content. A common complaint against XMLHTTPRequest in IE was that it doesn’t stream content. More specifically, the responseText property cannot be queried when readyState=3 (Receiving) and it only becomes available when readyState=4 (Loaded). This means that while your JavaScript will know when the transfer of the response body starts, you must wait for the response to complete before examining it. If your goal is to stream down a “never-ending” stream of data, you’ll find that IE’s XHR object never gets to the Loaded readyState and thus you cannot examine the “partial” response.