Chrome DevTools now supports *individual* network request throttling!
Folks have been asking for this for years! DevTools now allows developers to simulate slow network conditions for specific requests rather than the entire page.
This helps in testing how a web application performs and handles issues when specific resources (like images, scripts, or API calls) are slow to load.
For large values like JSONB, PostgreSQL uses the The Oversized Attribute Storage Technique (TOAST) mechanism
The original table only stores a small TOAST pointer to the external data.
PostgreSQL moves large data as chunks to a separate TOAST table
It's accessible by JS so if XSS happens, attacker can steal it.
There is No HttpOnly support there and you canโt block script access.
Some still use it because backend has no session system and SPA needs to attach token in headers easily.
Any Mitigations?
@tan_stack Query instances by default consider cached data as stale (staleTime=0).
So if a transition happens, the query's gonna fetch again. But if you don't want it to keep re-fetching, you can just set a longer staleTime. That way, it stays fresh longer and wonโt pull every time
If `gcTime=0` and `staleTime=0`, values are stale.
Stale values arenโt removed immediately they must first transition to an `inactive/unused` state.
This transition happens when a component or hook unmounts, or the query key changes.
#react#reactquery@tan_stack
#Docker Tip:
Need your container to access a specific :port on the host? If you're not using --network host, use the host's IP or host.docker.internal (OS-dependent). ๐