# Swipl.css is 404ed

**URL:** <https://swi-prolog.discourse.group/t/swipl-css-is-404ed/1604>\
**Category:** General\
**Created:** [December 11, 2019, 4:43pm UTC](https://swi-prolog.discourse.group/t/swipl-css-is-404ed/1604 "2019-12-11T16:43:53Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![dklyons81](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/dklyons81/32/29_2.png) [@dklyons81](https://swi-prolog.discourse.group/u/dklyons81)\
**Post date:** [December 11, 2019, 4:43pm UTC](https://swi-prolog.discourse.group/t/swipl-css-is-404ed/1604/1 "2019-12-11T16:43:53Z")

</div>

I’m getting a 404 on the swipl.css file, so the whole [swi-prolog.org](http://swi-prolog.org) site is looking fairly unstyled.

---

<div class="post-metadata">

**Author:** ![rausm](https://avatars.discourse-cdn.com/v4/letter/r/8e8cbc/32.png) [@rausm](https://swi-prolog.discourse.group/u/rausm)\
**Post date:** [December 11, 2019, 5:23pm UTC](https://swi-prolog.discourse.group/t/swipl-css-is-404ed/1604/2 "2019-12-11T17:23:36Z")

</div>

Weird, for me it looks normal, an the referenced swipl.css ([https://www.swi-prolog.org/css/swipl.css](https://www.swi-prolog.org/css/swipl.css)) is where it’s suposed to be.  
Maybe it got fixed fast.

---

<div class="post-metadata">

**Author:** ![dklyons81](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/dklyons81/32/29_2.png) [@dklyons81](https://swi-prolog.discourse.group/u/dklyons81)\
**Post date:** [December 11, 2019, 5:24pm UTC](https://swi-prolog.discourse.group/t/swipl-css-is-404ed/1604/3 "2019-12-11T17:24:20Z")

</div>

It appears to be working for me now too. Fast fix I guess.

---

<div class="post-metadata">

**Author:** ![jan](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/jan/32/4_2.png) [@jan](https://swi-prolog.discourse.group/u/jan)\
**Post date:** [December 11, 2019, 8:04pm UTC](https://swi-prolog.discourse.group/t/swipl-css-is-404ed/1604/4 "2019-12-11T20:04:45Z")

</div>

I’m afraid not. This has happened a few times. Seems like one of the backends misbehaves sometimes and the CDN things the CSS file is missing. After a cache invalidation time it will retry to access the backend and the problem is (usually) solved. I’ll check the log files.

In the meanwhile, the work-around is to access one of the two backends directly: [https://eu.swi-prolog.org](https://eu.swi-prolog.org) or [https://us.swi-prolog.org](https://us.swi-prolog.org). Please only use these for bypassing emergencies and do not advertise them as `better’ alternatives. Most of the times the CDN is more reliable and is a stable location. The backends can be accessed directly, but should be considered less stable and may at some point deny direct access.

---

<div class="post-metadata">

**Author:** ![jan](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/jan/32/4_2.png) [@jan](https://swi-prolog.discourse.group/u/jan)\
**Post date:** [December 12, 2019, 1:48pm UTC](https://swi-prolog.discourse.group/t/swipl-css-is-404ed/1604/5 "2019-12-12T13:48:30Z")

</div>

The log files tell me that both backends occasionally claim `/css/swipl.css` to be non-existent. Now the question is _why_ …

---

<div class="post-metadata">

**Author:** ![jan](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/jan/32/4_2.png) [@jan](https://swi-prolog.discourse.group/u/jan)\
**Post date:** [December 15, 2019, 4:17pm UTC](https://swi-prolog.discourse.group/t/swipl-css-is-404ed/1604/6 "2019-12-15T16:17:25Z")

</div>

Fixed with SWI-Prolog 8.1.18 (introduced in 8.1.11). Thanks for reporting. The underlying issue was rather critical.