Possible URLs for calling the internal webserver

The internal webserver of dinoex-iroffer is quite powerful and so have multiple urls to call it in order to obtain different kinds of lists. In the following we take a look at all possible ways. This assumes you have setuped the integrated webserver and rehashed/restarted to activate it.

1. http://<yourdomain/ip>:<yourport>/

Defaults to "xdcclistfile", can be configured.

2. http://<yourdomain/ip>:<yourport>/txt

The most baisc way to call the weblist from the webserver. It gives you back a basic textfile like list, similar to the output of "xdcclistfile" in the config file. To be able to use this url it's required to have the "xdcclistfile" setting activated in the config file.

3. http://<yourdomain/ip>:<yourport>/?

This calls the html-based weblist. This weblist is html-based and requires you to have the files "header.html", "footer.html" inside the bots base directory, additional you need to have "http_dir" in the config set and activated. In the folder you defined with "http_dir" should lie the file iroffer-state.css, otherwise the weblist gets shown unstyled. Additionally you can use all those files to customise the weblist design.

4. http://<yourdomain/ip>:<yourport>/xml

This give you a XML-file back with all the packs on the bot featuring size, group, name, md5/crc32 checksum. The size data comes in 2 ways, as bytes and rounded to MB. To be able to use this url it's required to have the "xdccxmlfile" setting activated in the config file.

5. http://<yourdomain/ip>:<yourport>/<yourrubyscript.rb>

This let you execute a ruby-script with the extension .rb as CGI-script. To be able to use this its required to have the bot compiled with the option "-ruby" at configure stage to activate the ruby support in the bot. The script must be located in the directory defined with the "http_dir" setting in the config.

6. http://<yourdomain/ip>:<yourport>/<yourfile.ext>

It's also be possible to serve out all kinds of files using the internal webserver, but always remember those files gets plain send out to the client. This means they wont get executed or interpreted ahead (except ruby scripts when the above descriped case takes place). So this can be used to hand out for example torrent-files or similar.

Also applying to all URLs if you use GeoIP are the restrictions set in your config file. This means GeoIP is compiled in with the option "-geoip" at the configure state, and "http_geoip" is set within the config, all the geoip restrictions also work for the internal webserver. Keep this in mind if you make use of GeoIP and maybe having problems accessing your weblist.