Consistently serve useful things as text

[ghost]

I'm not exactly sure what the problem is, but please observe how [0] is served as text, whilst [1] is not. This means that users need to download [1] to read it. This is inconvenient e.g. when doing QA on a package repository.

[0] http://hackage.haskell.org/package/random-1.0.1.1/random.cabal
[1] http://hackage.haskell.org/package/fastcgi-3001.0.2.4/src/fastcgi.cabal

[hesselink]

Ah, so the cabal file server from the direct link on the package page is served as text/plain, while the one you get by following the 'browse' link gives you application/x-cabal. I'm pretty sure this comes from Happstack's default mime map.

[ghost]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 04/01/14 21:28, Erik Hesselink wrote:

Ah, so the cabal file server from the direct link on the package
page is served as text/plain, while the one you get by following
the 'browse' link gives you application/x-cabal. I'm pretty sure
this comes from Happstack's [default mime map].
Sounds like a reasonable conclusion

---

Alexander
[email protected]
http://plaimi.net/~alexander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlLIb3YACgkQRtClrXBQc7U9mgEAgYDCM+aZ3FGS/4S07YUTW/8G
YaC+R3Gm+dVs+ZQro3oA/iVrZH35Hhe2ZVwI026iHzuOx5MtshYDlUt/9g9EenLe
=Ux47
-----END PGP SIGNATURE-----