545563e776
- Complete NestJS TypeScript implementation with WebSocket support - Direct messaging (DM) and group chat functionality - End-to-end encryption with AES encryption and key pairs - Media file support (images, videos, audio, documents) up to 100MB - Push notifications with Firebase Cloud Messaging integration - Mention alerts and real-time typing indicators - User authentication with JWT and Passport - SQLite database with TypeORM entities and relationships - Comprehensive API documentation with Swagger/OpenAPI - File upload handling with secure access control - Online/offline status tracking and presence management - Message editing, deletion, and reply functionality - Notification management with automatic cleanup - Health check endpoint for monitoring - CORS configuration for cross-origin requests - Environment-based configuration management - Structured for Flutter SDK integration Features implemented: ✅ Real-time messaging with Socket.IO ✅ User registration and authentication ✅ Direct messages and group chats ✅ Media file uploads and management ✅ End-to-end encryption ✅ Push notifications ✅ Mention alerts ✅ Typing indicators ✅ Message read receipts ✅ Online status tracking ✅ File access control ✅ Comprehensive API documentation Ready for Flutter SDK development and production deployment.
97 lines
4.2 KiB
Markdown
97 lines
4.2 KiB
Markdown
# html-escaper [](https://travis-ci.org/WebReflection/html-escaper) [](https://coveralls.io/github/WebReflection/html-escaper?branch=master)
|
|
A simple module to escape/unescape common problematic entities.
|
|
|
|
|
|
### How
|
|
This package is available in npm so `npm install html-escaper` is all you need to do, using eventually the global flag too.
|
|
|
|
Once the module is present
|
|
```js
|
|
var html = require('html-escaper');
|
|
|
|
// two basic methods
|
|
html.escape('string');
|
|
html.unescape('escaped string');
|
|
```
|
|
|
|
|
|
### Why
|
|
there is basically one rule only: do not **ever** replace one char after another if you are transforming a string into another.
|
|
|
|
```js
|
|
// WARNING: THIS IS WRONG
|
|
// if you are that kind of dev that does this
|
|
function escape(s) {
|
|
return s.replace(/&/g, "&")
|
|
.replace(/</g, "<")
|
|
.replace(/>/g, ">")
|
|
.replace(/'/g, "'")
|
|
.replace(/"/g, """);
|
|
}
|
|
|
|
// you might be the same dev that does this too
|
|
function unescape(s) {
|
|
return s.replace(/&/g, "&")
|
|
.replace(/</g, "<")
|
|
.replace(/>/g, ">")
|
|
.replace(/'/g, "'")
|
|
.replace(/"/g, '"');
|
|
}
|
|
|
|
// guess what we have here ?
|
|
unescape('&lt;');
|
|
|
|
// now guess this XSS too ...
|
|
unescape('&lt;script&gt;alert("yo")&lt;/script&gt;');
|
|
|
|
|
|
```
|
|
|
|
The last example will produce `<script>alert("yo")</script>` instead of the expected `<script>alert("yo")</script>`.
|
|
|
|
Nothing like this could possibly happen if we grab all chars at once and either ways.
|
|
It's just a fortunate case that after swapping `&` with `&` no other replace will be affected, but it's not portable and universally a bad practice.
|
|
|
|
Grab all chars at once, no excuses!
|
|
|
|
|
|
|
|
**more details**
|
|
As somebody might think it's an `unescape` issue only, it's not. Being an anti-pattern with side effects works both ways.
|
|
|
|
As example, changing the order of the replacement in escaping would produce the unexpected:
|
|
```js
|
|
function escape(s) {
|
|
return s.replace(/</g, "<")
|
|
.replace(/>/g, ">")
|
|
.replace(/'/g, "'")
|
|
.replace(/"/g, """)
|
|
.replace(/&/g, "&");
|
|
}
|
|
|
|
escape('<'); // &lt; instead of <
|
|
```
|
|
If we do not want to code with the fear that the order wasn't perfect or that our order in either escaping or unescaping is different from the order another method or function used, if we understand the issue and we agree it's potentially a disaster prone approach, if we add the fact in this case creating 4 RegExp objects each time and invoking 4 times `.replace` trough the `String.prototype` is also potentially slower than creating one function only holding one object, or holding the function too, we should agree there is not absolutely any valid reason to keep proposing a char-by-char implementation.
|
|
|
|
We have proofs this approach can fail already so ... why should we risk? Just avoid and grab all chars at once or simply use this tiny utility.
|
|
|
|
### Backtick
|
|
Internt explorer < 9 has [some backtick issue](https://html5sec.org/#102)
|
|
|
|
For compatibility sake with common server-side HTML entities encoders and decoders, and in order to have the most reliable I/O, this little utility will NOT fix this IE < 9 problem.
|
|
|
|
It is also important to note that if we create valid HTML and we set attributes at runtime through this utility, backticks in strings cannot possibly affect attribute behaviors.
|
|
|
|
```js
|
|
var img = new Image();
|
|
img.src = html.escape(
|
|
'x` `<script>alert(1)</script>"` `'
|
|
);
|
|
// it won't cause problems even in IE < 9
|
|
```
|
|
|
|
**However**, if you use `innerHTML` and you target IE < 9 then [this **might** be a problem](https://github.com/nette/nette/issues/1496).
|
|
|
|
Accordingly, if you need more chars and/or backticks to be escaped and unescaped, feel free to use alternatives like [lodash](https://github.com/lodash/lodash) or [he](https://www.npmjs.com/package/he)
|
|
|
|
Here a bit more of [my POV](https://github.com/WebReflection/html-escaper/commit/52d554fc6e8583b6ffdd357967cf71962fc07cf6#commitcomment-10625122) and why I haven't implemented same thing alternatives did. Good news: those are alternatives ;-) |