ejabberd - Comments for "Serving crossdomain.xml with mod_http_fileserver"

That was it, thanks badlop!

aaronwinborn — Mon, 05 Apr 2010 19:03:12 +0000

That was it, thanks badlop!

Old ejabberd version, probably doesn't implement the options

mfoss — Mon, 05 Apr 2010 18:12:29 +0000

aaronwinborn wrote:

This is ejabberd v. 2.0.0 by the way.

Maybe the module you are running doesn't yet implement those options. Check the ejabberd Guide included in that exact version.

I see that the ticket Allow content types to be configured in ejabberd.cfg was implemented in ejabberd 2.1.0

As a test, I just recompiled

aaronwinborn — Mon, 05 Apr 2010 17:14:16 +0000

As a test, I just recompiled mod_http_fileserver from ejabberd_modules (the 2.0.x version) and swapped that with the version at /usr/lib/ejabberd/ebin/mod_http_fileserver.beam, with no effect on behavior. Frustrating.

Negative tests work as

aaronwinborn — Mon, 05 Apr 2010 16:35:28 +0000

Negative tests work as expected, serving a 404 when disabled.

Oddly, if I comment out the mod_http_fileserver from modules, but leave the listening port, I now get

HTTP/0.9 200 OK

for them all, regardless of whether a file exists, but 0 bytes of course.

All settings ignored...

aaronwinborn — Mon, 05 Apr 2010 16:29:23 +0000

Apparently, any settings I have for content_type has no effect.

Here are the tests I've run:

I put "test.html", "test.png" and "test.blah" files in addition to the crossdomain.xml file in /home/my-user/web (not using /var/www since that's apache's home, even though apache's not installed).

{5280, ejabberd_http, [
                        web_admin,
                         {request_handlers,     [{["xmpp-httpbind"],
                                                 mod_http_bind},
                                                {[], mod_http_fileserver}
                                                ]}
                        ]}

and

  {mod_http_fileserver, [{docroot, "/home/xomba/web"},
                  {content_types, [{".xml", "text/xml"}, {".png", "experimental/blah"}, {".blah", "nothing/here"}]},
                  {default_content_type, "text/xml"}
                 ]},

Headers for each:

crossdomain.xml (Expected text/xml)

HTTP/1.1 200 OK
Content-Type: application/octet-stream
Content-Length: 323
Server: ejabberd
Last-Modified: Fri, 02 Apr 2010 20:44:19 GMT

test.html (Expected either application/octet-stream or text/xml depending on whether default_content_type caught it)

HTTP/1.1 200 OK
Content-Type: text/html
Content-Length: 8
Server: ejabberd
Last-Modified: Mon, 05 Apr 2010 16:13:09 GMT

test.png (expected experimental/blah)

HTTP/1.1 200 OK
Content-Type: image/png
Content-Length: 12453
Server: ejabberd
Last-Modified: Mon, 05 Apr 2010 16:15:31 GMT

test.blah (expected nothing/here)

HTTP/1.1 200 OK
Content-Type: application/octet-stream
Content-Length: 11
Server: ejabberd
Last-Modified: Mon, 05 Apr 2010 16:23:54 GMT

This is ejabberd v. 2.0.0 by

aaronwinborn — Mon, 05 Apr 2010 16:07:37 +0000

This is ejabberd v. 2.0.0 by the way.

default_content_type

aaronwinborn — Mon, 05 Apr 2010 16:03:27 +0000

I've also tried to set default_content_type. Still coming up as application/octet-stream...

  {mod_http_fileserver, [{docroot, "/var/www"},
                  {content_types, [{".xml", "text/xml"}]},
                  {default_content_type, "text/xml"}
                 ]},

Regardless of the

aaronwinborn — Mon, 05 Apr 2010 15:37:06 +0000

Regardless of the content_types setting, I'm getting the following. That's after modifying the cfg file and restarting ejabberd of course.

http://xmpp.example.com:5280/crossdomain.xml
HTTP/1.1 200 OK
Content-Type: application/octet-stream
Content-Length: 323
Server: ejabberd
Last-Modified: Fri, 02 Apr 2010 20:44:19 GMT

aaronwinborn wrote: {5280,

mfoss — Sat, 03 Apr 2010 17:54:09 +0000

aaronwinborn wrote:

  {5280, ejabberd_http, [
                        web_admin,
                         {request_handlers,     [{["xmpp-httpbind"],
                                                 mod_http_bind},
                                                {[], mod_http_fileserver}
                                                ]}
                        ]}

this configuration also disabled the web_admin functionality.

Right, I see that problem too. A solution is to indicate explicitely the webadmin, see as example:

  {5280, ejabberd_http, [
                         {request_handlers,     [
                            {["xmpp-httpbind"], mod_http_bind},
                            {["admin"], ejabberd_web_admin},
                            {[], mod_http_fileserver}
                         ]}
                        ]},

The option works for me

mfoss — Sat, 03 Apr 2010 17:48:48 +0000

If I configure the module without the content_type option, I get:

$ lynx http://localhost:5280/crossdomain.xml -mime_header
HTTP/1.0 200 OK
Connection: close
Content-Length: 221
Server: ejabberd
Last-Modified: Sat, 03 Apr 2010 17:40:43 GMT
Content-Type: application/octet-stream

...

If I configure some rare type:

  {mod_http_fileserver, [
    {docroot, "/tmp"}, 
    {content_types, [{".xml", "texXxt/xm123l"}]}
  ]},

I get it as configured:

$ lynx http://localhost:5280/crossdomain.xml -mime_header
HTTP/1.0 200 OK
Connection: close
Content-Length: 221
Server: ejabberd
Last-Modified: Sat, 03 Apr 2010 17:40:43 GMT
Content-Type: texXxt/xm123l

...