# HTTP-caching LiveView's first render

**URL:** <https://forum.elixirforum.com/t/http-caching-liveviews-first-render/59180>\
**Category:** Questions\
**Tags:** phoenix, liveview, caching\
**Created:** [October 22, 2023, 9:08pm UTC](https://forum.elixirforum.com/t/http-caching-liveviews-first-render/59180 "2023-10-22T21:08:16Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![tangui](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/tangui/32/12091_2.png) [@tangui](https://forum.elixirforum.com/u/tangui)\
**Post date:** [September 2, 2024, 1:16pm UTC](https://forum.elixirforum.com/t/http-caching-liveviews-first-render/59180/9 "2024-09-02T13:16:02Z")

</div>

> [@onnimonni](#):
>
> Thanks @tangui for your great blog post regarding http caching Liveview pages: [Caching Liveviews - Part 1: The road to HTTP-caching Liveviews - Tangui’s blog](https://svground.fr/blog/posts/caching-liveviews-part-1/)

I’ll publish the second part (_Caching Liveviews - Part 2: Publicly caching private Liveviews_) this week.

> [@onnimonni](#):
>
> I’m eagerly waiting for the next blog posts already 💪. I saw that you needed to create your own fork of Phoenix. Did you create a pull-request to phoenix core to allow disabling the csrf tokens?

I tried earlier this year but the PR was unclear and not great TBH. It’d be nice if some devs with security expertise could confirm the hypothesis I’ve made in the post (that is, you can safely rely on `origin` only). I’ll open the PR this month anyway and keep the community informed in this post 👍

---

_[View the full topic](https://forum.elixirforum.com/t/http-caching-liveviews-first-render/59180)._