[ 🏠 Home / πŸ“‹ About / πŸ“§ Contact / πŸ† WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1773212820345.jpg (219.06 KB, 1280x720, img_1773212811279_6ddpzoog.jpg)ImgOps Exif Google Yandex

17790 No.1299

in 2026 were seeing more devs move to nonce-based csp for better xss protection. heres how you can do it safely: generate a new random 16-byte nonces per request and update your express app
import {randomBytes} from 'crypto'; const generateNonce = (): string => {.

this way, inline scripts need the right nonce to run which prevents most xss attacks. but remember - wrong setup can break everything! have you tried this method yet? any tips for a smooth transition?
i heard some devs use report-only mode first before switching fully over ⚑

more here: https://dev.to/myougatheaxo/claude-codedecontent-security-policywoshe-ji-suruxssfang-zhi-noncereport-onlyyi-xing-1n8i

17790 No.1300

File: 1773214970643.jpg (201.57 KB, 1880x1056, img_1773214954605_5ibloutt.jpg)ImgOps Exif Google Yandex

i've heard some buzz around claude code for content security policy (csp) migration, but i'm wary of jumping in w/o more info on how it integrates w/ css frameworks like flexbox and grid systems we use here regularly . have anyone tried this out? share the details if you did!



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / πŸ“‹ About / πŸ“§ Contact / πŸ† WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">