# Write.as uses an old, insecure version of Nginx

**URL:** <https://discuss.write.as/t/write-as-uses-an-old-insecure-version-of-nginx/1479>\
**Category:** Feature requests\
**Tags:** 🛳-released, troubleshooting\
**Created:** [June 2, 2020, 3:23pm UTC](https://discuss.write.as/t/write-as-uses-an-old-insecure-version-of-nginx/1479 "2020-06-02T15:23:42Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![nxfury](https://discuss.write.as/letter_avatar_proxy/v4/letter/n/ce73a5/32.png) [@nxfury](https://discuss.write.as/u/nxfury)\
**Post date:** [June 2, 2020, 3:23pm UTC](https://discuss.write.as/t/write-as-uses-an-old-insecure-version-of-nginx/1479/1 "2020-06-02T15:23:42Z")

</div>

Hey guys!

So I’m a paid subscriber of Write.as and I use it for my blog. I performed a routine security audit on my infrastructure and noticed that the version of Nginx that Write.as ships with their version of Write Freely is outdated and insecure. Are there any plans to update this to the latest version in the name of being privacy-respecting? Thanks!

---

<div class="post-metadata">

**Author:** ![nxfury](https://discuss.write.as/letter_avatar_proxy/v4/letter/n/ce73a5/32.png) [@nxfury](https://discuss.write.as/u/nxfury)\
**Post date:** [June 18, 2020, 2:28pm UTC](https://discuss.write.as/t/write-as-uses-an-old-insecure-version-of-nginx/1479/2 "2020-06-18T14:28:30Z")

</div>

Is there any news regarding this?

---

<div class="post-metadata">

**Author:** ![kxra](https://discuss.write.as/user_avatar/discuss.write.as/kxra/32/958_2.png) [@kxra](https://discuss.write.as/u/kxra)\
**Post date:** [February 25, 2021, 10:29pm UTC](https://discuss.write.as/t/write-as-uses-an-old-insecure-version-of-nginx/1479/3 "2021-02-25T22:29:04Z")

</div>

Might be nice to enable HTTP2 support as well. I was recently asking about how things are hosted

> Is Write.as served by Nginx, Apache, or something like that? I noticed that [testmysite.io](http://testmysite.io) reports that HTTP2 is not enabled, but should be a one-line fix in Nginx config or there’s the more bleeding-edge approach [https://h2o.examp1e.net/](https://h2o.examp1e.net/) 😉

---

<div class="post-metadata">

**Author:** ![18percentgrey](https://discuss.write.as/user_avatar/discuss.write.as/18percentgrey/32/697_2.png) [@18percentgrey](https://discuss.write.as/u/18percentgrey)\
**Post date:** [February 27, 2021, 6:04am UTC](https://discuss.write.as/t/write-as-uses-an-old-insecure-version-of-nginx/1479/4 "2021-02-27T06:04:29Z")

</div>

interesting . imho theres far too much uncertainty already introduced by stuff like standardizing ssl via dns and all of the emergent things which go against the general grain of the ietf draftspecs and some things cern is working on / working out… this would only add a wee bit much too much complexity and the potential for fractalized loci therein with respect to the experiential topology would decimate a potential macro adoption curve, or a useful trackable one for solid development.

too many kinds of soup noodles ruins software interoperability and congruence, whereas with human expression it is quite desirous.

hope that perspective helps a bit.

---

<div class="post-metadata">

**Author:** ![kxra](https://discuss.write.as/user_avatar/discuss.write.as/kxra/32/958_2.png) [@kxra](https://discuss.write.as/u/kxra)\
**Post date:** [February 27, 2021, 4:19pm UTC](https://discuss.write.as/t/write-as-uses-an-old-insecure-version-of-nginx/1479/5 "2021-02-27T16:19:18Z")

</div>

The internet has grown and evolved a bit since HTTP1.1 sadly haha

HTTP/2 has been an approved IETF spec for years and is already widely apoted. There’s not a more popular standard that this is trying to competed with. This is the mainstream.

> **[HTTP/2 | 2019 | The Web Almanac by HTTP Archive](https://almanac.httparchive.org/en/2019/http)**
>
> HTTP/2 chapter of the 2019 Web Almanac covering adoption and impact of HTTP/2, HTTP/2 Push, HTTP/2 Issues, and HTTP/3.

Not asking for an implementation, just a config file change to enable something already implemented in the server software.

> [@18percentgrey](#):
>
> fractalized loci

Fractalized loci of what?

---

<div class="post-metadata">

**Author:** ![18percentgrey](https://discuss.write.as/user_avatar/discuss.write.as/18percentgrey/32/697_2.png) [@18percentgrey](https://discuss.write.as/u/18percentgrey)\
**Post date:** [February 27, 2021, 4:44pm UTC](https://discuss.write.as/t/write-as-uses-an-old-insecure-version-of-nginx/1479/6 "2021-02-27T16:44:37Z")

</div>

OH!!! its the updated draftspec. pardon me i understand this now. thank you. 🙂

loci of users- that remark is now irrelevant by the updated understanding of what you were actually talking about. 😆

---

<div class="post-metadata">

**Author:** ![matt](https://discuss.write.as/user_avatar/discuss.write.as/matt/32/2760_2.png) [@matt](https://discuss.write.as/u/matt)\
**Post date:** [January 24, 2022, 5:50pm UTC](https://discuss.write.as/t/write-as-uses-an-old-insecure-version-of-nginx/1479/7 "2022-01-24T17:50:46Z")

</div>

Just a heads up that we’re running a more up-to-date version of nginx now, and have enabled HTTP2!
