#server-side

HashiCorp patched CVE-2026-0969 in next-mdx-remote, which allowed arbitrary server-side code execution when compiling untrusted MDX content with JavaScript enabled.

Source: Socket

Sometimes, JavaScript modification doesn’t reflect on the page while running.

Need to clear browser cache manually each time when the file gets updated.

It makes the debugging process hard.

If the project contains some bug and you fix it but the user needs to clear the browser cache to reflect the changes.

If you run a blog, you probably check your analytics regularly. Pageviews, traffic sources, time on page - these numbers guide your content decisions, your SEO strategy, and sometimes your ad revenue conversations.

But there is a good chance those numbers are lower than reality.

Not because your blog is underperforming. Because a growing share of your readers is invisible to your analytics tool - and you have no way of knowing how large that share actually is.

Why blog analytics has a measurement problem

Most blogs track visitors through browser-based tags - small JavaScript snippets that fire when a page loads and send data to analytics platforms like Google Analytics. The system works well in ideal conditions.

Ideal conditions are increasingly rare.

Around 40% of internet users worldwide use ad-blocking software, according to Statista. Most ad blockers suppress analytics scripts alongside ad requests. Safari's Intelligent Tracking Prevention limits how long tracking cookies persist. Firefox applies similar defaults. And readers who browse in private or incognito mode generate sessions that cannot be connected to previous visits.

The result is a systematic gap between your actual readership and what your analytics dashboard reports. For bloggers who monetize through display advertising or sponsored content, that gap understates the audience you are actually delivering to advertisers.

What server-side tags are and why they change the picture

A server-side tag does not run in the reader's browser. It runs on a server - either your own or one managed on your behalf. When a reader visits a post, the event is captured at the server level and forwarded to your analytics platform from there.

The reader's browser settings, ad blockers, and cookie preferences do not affect what the server records. The visit gets logged regardless.

For a server-side analytics setup, this means the data flowing into your reports reflects your real traffic - not the portion that happened to pass through browser-side tracking unchallenged.

The practical difference is visible immediately when teams switch. Blogs that move from browser-only to server-side tracking consistently report higher session counts on the same traffic - not because readership grew, but because previously invisible readers are now being counted.

What better data actually changes for bloggers

More accurate traffic numbers affect several things at once.

Content decisions. When you can see which posts drive genuine return visits - not just first-time pageviews - you get a clearer picture of what your audience actually values. A post that looks average in cookie-dependent analytics might be a consistent driver of repeat traffic when measured completely.

SEO strategy. Understanding which traffic sources bring readers who stay and engage, versus those who bounce immediately, helps prioritize where to focus. If organic search is driving high-quality readers that previously went uncounted, that changes how you allocate time between SEO and other channels.

Ad revenue conversations. If your blog carries display ads or you negotiate sponsored content deals, your reported audience size matters. Analytics that capture your full readership - rather than the consented, non-blocking subset - gives you accurate numbers to bring to those conversations.

Page speed: the side benefit most bloggers overlook

Browser-based tags have a performance cost. Every JavaScript tag that loads in the reader's browser adds weight to the page. Multiple analytics and marketing tags running simultaneously can slow load times noticeably, particularly on mobile connections.

Server-side tags move that processing off the reader's device. The browser loads a lighter page. Tag logic executes on the server instead. For blogs where page speed affects both reader experience and search rankings, that shift has a measurable impact.

Google's Core Web Vitals - the page experience signals that factor into search rankings - include load speed as a component. Reducing browser-side tag weight is one of the more straightforward ways to improve those scores without redesigning the site.

A realistic picture of what the transition involves

Server-side tagging sounds technical, and the underlying infrastructure is. But for bloggers and content marketers without a developer background, the relevant question is not how it works mechanically - it is what it takes to get started.

Managed server-side analytics platforms handle the infrastructure side. The blogger connects their existing analytics setup to the server-side layer, and data starts flowing through the new path. Most setups involve a configuration process rather than custom code, and existing dashboards continue working with more complete data feeding into them.

The transition does not require rebuilding your analytics from scratch. It adds a more reliable data collection layer underneath what you already have.

What the numbers look like after

Teams that have made the switch report a consistent pattern: the gap between server-side and browser-side event counts is larger than expected. Depending on the audience and the share of ad-blocking users among readers, the difference can range from 15% to over 40% of total sessions.

What is PHP?...

PHP (repeated abbreviation for PHP: Hypertext Pre-processor - The Supertitle Pre-processor) is a subset of programming languages such as JavaScript and Python. The difference is that PHP is generally used for server-side communication, while JavaScript is used for both front-end and back-end. Python is only used for the client side (back-end).

For example, you can validate the form using a script to make sure all section are filled in before a form goes to the server. The script runs when a user submits the form and checks all sections.

https://shareurcodes.com/blog/creating%20a%20simple%20rest%20api%20in%20php

https://www.cheatography.com/davechild/cheat-sheets/mod-rewrite/

https://www.regexpal.com/