http-server

Create reusable HTTP server daemons for Oxidus LPC environments.

8|3|Updated Sep 29, 2021
One-click install
npx skills add https://github.com/gesslar/oxidus-mudlib --skill http-server
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: http-server
Source: https://github.com/gesslar/oxidus-mudlib/tree/main/.claude/skills/http-server
Command: npx skills add https://github.com/gesslar/oxidus-mudlib --skill http-server

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a reusable HTTP server daemon base for Oxidus LPC environments, standardizing port binding, request handling, TLS, deflate compression, and connection management.

Core Features & Use Cases

  • Inherit STD_HTTP_SERVER to create a custom HTTP daemon that can listen on a port and accept requests.
  • Supported capabilities include TLS for secure connections, deflate compression for efficient responses, and a structured request/response lifecycle via http_handle_request().
  • Use cases include building lightweight API endpoints, status dashboards, or internal services that respond to HTTP(S) requests from Oxidus daemons.

Quick Start

Inherit STD_HTTP_SERVER, configure the listen port, implement http_handle_request, and call start_server.

Frequently Asked Questions about http-server

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build an HTTP server in an Oxidus LPC environment?

You can create an HTTP server daemon by inheriting STD_HTTP_SERVER, defining a listen port, and implementing http_handle_request to process incoming requests and return responses.

Does the Oxidus HTTP server daemon support TLS and compression?

Yes, the Oxidus HTTP server daemon supports TLS for secure encrypted connections and deflate compression to optimize response payloads sent to HTTP clients.

Can I run multiple HTTP server daemons on different ports simultaneously?

Yes, the skill provides robust connection management across multiple daemons, allowing you to configure separate listen ports and run several HTTP server instances concurrently in Oxidus.

What is required to handle HTTP requests in an Oxidus LPC daemon?

Handling HTTP requests requires inheriting STD_HTTP_SERVER, configuring the listen port, and implementing the http_handle_request function to process the structured request and response lifecycle.

How do I close an HTTP server connection in Oxidus LPC?

To close an HTTP server connection in Oxidus LPC, use the close operation provided by STD_HTTP_SERVER to manage the server lifecycle and terminate active connections.