Project

General

Profile

Actions

Feature #1013

closed

Configure Busybox httpd for use with piboxwww

Added by Hammel 9 months ago. Updated 7 months ago.

Status:
Closed
Priority:
Immediate
Assignee:
Category:
Web Server
Target version:
Start date:
31 Jul 2023
Due date:
% Done:

100%

Estimated time:
Severity:
02 - High

Description

This is to check the value of switching from Monkey to Busybox httpd (as opposed to lighttpd).


Related issues

Related to piboxwww - Bug #1040: Investigate alternatives to Monkey as a web serverClosedHammel23 Sep 2023

Actions
Actions #2

Updated by Hammel 8 months ago

  • Severity changed from 05 - Very Low to 02 - High
Actions #3

Updated by Hammel 7 months ago

I don't see anything that says Busybox httpd supports and external authentication file, like htpasswd. Instead, users and passwords are embedded in the httpd.conf file. I don't want that. I want to seperate server config from authentication data.

I'm now looking at other options.

Actions #4

Updated by Hammel 7 months ago

  • Related to Bug #1040: Investigate alternatives to Monkey as a web server added
Actions #5

Updated by Hammel 7 months ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Busybox httpd will not be used - lighttpd proved to be a better solution.

See RM #1040 and RM #1014.

Busybox httpd removed from build configuration.
Change committed and pushed.

Closing issue.

Actions

Also available in: Atom PDF