|
Bugzilla – Full Text Bug Listing |
| Summary: | HTTP Server Configuration, Parse Error | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Jeffrey Walton <noloader> |
| Component: | YaST2 | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | eduar.cardona |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | openSUSE 11.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | HTTP Server Config Parse after selecting 127.0.0.1:80 | ||
Comment on attachment 286037 [details]
HTTP Server Config Parse after selecting 127.0.0.1:80
PNG file is attached. I'm not sure how I managed to drop the extension between the screen capture and upload.
File of interest in listen.conf When binding to 'All Addresses', entry is: * Listen 80 When binding to an IP/Port, entry is: * Listen 127.0.0.1:80 or * Listen 192.168.1.30:80 reproduced fixed in yast2-http-server-2.18.8 *** Bug 491996 has been marked as a duplicate of this bug. *** |
Created attachment 286037 [details] HTTP Server Config Parse after selecting 127.0.0.1:80 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.1.1 Firefox/3.0.8 HTTP Server Configuration incorrectly parses the configuration file when Apache2 is bound to the local address of 127.0.0.1. See attached. Note that this machine has eth0 and wlan0. But the settings of (ie, binding to) wlan0 does not appear to effect the problem. Removing the card may remedy, but the machine is not scheduled for maintenance any time soon. eth0 is receiving a DHCP address from a separate server. wlan0 is harcode (but different subnet. Current configuration is eth0: 192.168.1.32/24 wlan0: 192.168.2.30/24 Reproducible: Always Steps to Reproduce: 1. Open Yast 2. Select Network Services 3. Select HTTP Server 4. Add/Edit to 127.0.0.1 and port 80 5. Close HTTP Server 6. Reopen HTTP Server Actual Results: Odd parse Expected Results: Good parse