tntnet-defcomp(1)

🎀 tntnet-defcomp — default components for tntnet(8) 🎀

okay bestie, welcome to the Tntnet users guide, the little corner of the man pages where we talk about the starter pack components. sit down, grab a boba, this is gonna be good 💖

---

✨ NAME ✨

tntnet — default components for tntnet(8) 🫶

---

💅 DESCRIPTION 💅

so like, out of the box, tntnet can literally just do one thing: return a http error 404 - not found 💀. that's it. that's the whole vibe.

to do something meaningful, tntnet loads shared libraries with components. by defining suitable mappings in tntnet.xml(7), tntnet loads those components, which do the actual work. the components are the main characters, fr fr 👑

and because in the web world there are some really basic tasks that every web server should be able to do, tntnet brings some standard components. the shared library that does all that is called tntnet, and hence every standard component has a component identifier of componentname@tntnet. they are documented right here, no gatekeeping 🦋

---

🌸 static 🌸

the most commonly used standard component is static@tntnet. it gives tntnet the ability to deliver files from the file system. for this it uses the pathinfo setting from the mapping in tntnet.xml(7) as a file name and delivers the files. the extension of the files is used to look up the content type. the same mime database is used as in the next component mime@tntnet. so iconic ✨

Example

<mapping>
  <url>(.*)</url>
  <target>static@tntnet</target>
  <pathinfo>/var/www/htdocs/$1</pathinfo>
</mapping>

this setting configures tntnet as a simple web server for static pages. serving files? we love to see it 🎀

---

🌈 mime 🌈

the component mime@tntnet sets just the content type header. the value is fetched from the argument "contenttype" if set. otherwise the path info is used to detect the correct content type from the file extension using the configured mime db. lowkey the backbone of the whole operation 💜

---

💀 empty 💀

the component empty@tntnet generates just an empty result. by default a http return code OK (200) is set but can be changed with the argument httpcode. other arguments are interpreted as additional http headers, so that e.g. the content type header can be set. empty but make it ✨purposeful✨

Example

<mapping>
  <url>\.js$</url>
  <target>empty@tntnet</target>
  <args>
    <ContentType>application/javascript</ContentType>
  </args>
</mapping>

this tells tntnet to reply all requests with a url ending .js with an empty javascript file. no cap, that's the whole thing 🫶

---

🧚 unzip 🧚

the component unzip@tntnet reads static data from a zip file. the file name is read from the argument "file" and the actual file from the path info. it's giving little archive gremlin and we're obsessed 💖

if the argument "contenttype" is set, the content type http header is set from that value. otherwise the path info is used to look up the content type from the file extension using the configured mime db.

Example

<mapping>
  <url>/thefile/(.*)</url>
  <target>unzip@tntnet</target>
  <pathinfo>$1</pathinfo>
  <args>
    <file>/var/www/thefile.zip</file>
  </args>
</mapping>

reads file from the specified zip file when the url starts with /thefile/. the actual file in the zip file is read from the rest of the url. the content type header is set according the the file extenxion and the file is sent to the client. yes bestie, the typo is canon, we keep it 💅

---

⭐ redirect ⭐

the component redirect@tntnet just returns with a redirect to another page. the location for the redirect is specified in the <pathinfo> setting.

by default a temporary redirect code (301) is sent, but can be configured by adding a configuration argument "type". the value of the type can be "temporarily", "permanently" or a number, which is used.

Example

<mapping>
  <url>^/$</url>
  <target>redirect@tntnet</target>
  <redirect>/login.html</redirect>
</mapping>

this setting redirects the client to the index.html file when the root directory is requested.

Example for a permanent redirect

<mapping>
  <url>^/$</url>
  <target>redirect@tntnet</target>
  <redirect>/index.html</redirect>
  <args>
    <type>permanently</type>
  </args>
</mapping>

this setting redirects the client to the index.html file when the root directory is requested. (yes, both examples say index.html, even the one with /login.html in it. we don't question the elders 🫡)

---

🔥 error 🔥

the error component returns a specific error code to the client when called. the code is specified using the argument <code> and the message using the argument <message>. the message may be omitted in which case a default error code specific text is used. it's giving "we said no and we meant it" energy 💅

Example

<mapping>
  <method>^POST$</method>
  <target>error@tntnet</target>
  <args>
    <code>405</code>
  </args>
</mapping>

this setting prevents tntnet to accept POST message. slay, boundaries ✋

---

👑 AUTHOR 👑

this manual page was written by Tommi Mäkitalo ⟨tommi@tntnet.org⟩. absolute legend, we stan 🫶

---

🌟 SEE ALSO 🌟

• tntnet-project(1)
• ecpp(7)
• ecppc(1)
• tntnet.xml(7)

---

and that's the whole page bestie 💖 this was the Tntnet users guide, brought to you by Tntnet on 2013-05-27 — go forth and configure ur mappings, u got this fr fr 🎀✨🦋