# Cannot create .acl file because of Content-Type

**URL:** <https://forum.solidproject.org/t/cannot-create-acl-file-because-of-content-type/1955>\
**Category:** Solid App Development FAQs\
**Created:** [July 2, 2019, 8:48pm UTC](https://forum.solidproject.org/t/cannot-create-acl-file-because-of-content-type/1955 "2019-07-02T20:48:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dangvu](https://avatars.discourse-cdn.com/v4/letter/d/b38774/32.png) [@dangvu](https://forum.solidproject.org/u/dangvu)\
**Post date:** [July 2, 2019, 8:48pm UTC](https://forum.solidproject.org/t/cannot-create-acl-file-because-of-content-type/1955/1 "2019-07-02T20:48:40Z")

</div>

Hi,  
I am developing a solid application. In my app, when I create a new file, (data.txt) I want to create a new .acl for this file (data.txt.acl). However, when I don’t specify content-type, the .acl is created on the server but it cannot be accessed ( Error: Don’t know how to parse application/octet-stream yet while trying to parse \<[https://mypod](https://mypod)…/public/test/data.txt.acl\> as application/octet-stream). In contrast, if I specify content-type: ‘text/turle’ , the **.acl.ttl** will be created, instead of **.acl**. So, how can i fix it?

Here is what i have:

- solid server ([inrupt.net](http://inrupt.net)) version 5.1.4
- using solid-file-client

---

<div class="post-metadata">

**Author:** ![jeffz](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.solidproject.org/jeffz/32/600_2.png) [@jeffz](https://forum.solidproject.org/u/jeffz)\
**Post date:** [July 2, 2019, 9:01pm UTC](https://forum.solidproject.org/t/cannot-create-acl-file-because-of-content-type/1955/2 "2019-07-02T21:01:35Z")

</div>

Version 5.x of NSS has changed the way that file extensions are handled and there are several unresolved issues which the developers are working on. See [https://github.com/solid/node-solid-server/issues/1246](https://github.com/solid/node-solid-server/issues/1246). If you can, it may be best to wait a few days to see if this can get resolved. I am working on an updated version of solid-file-client but it isn’t ready yet. In the meantime, you may have better success with fileClient.fetch( foo, {method:“PUT”,… headers including content-type}).