|
Bugzilla – Full Text Bug Listing |
| Summary: | virtual http-server setup erraneous | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Christian Stüben <cs.st.ng> |
| Component: | YaST2 | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | cs.st.ng |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | openSUSE 10.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Christian Stüben
2007-08-10 12:45:26 UTC
Hi Chris, can you provide me how to "step-by-step" reproduce this problem? As I understand you mean when you edit already configured one - this is fixed for 10.3 ... And next-back is fixed in yast2-http-server-2.15.7 (for 10.3 Beta2) Hi Michael, unfortunately the server with suse 10.2 is no more standing at my location. So i will try to tell from my memories ... When entering yast, going to the setup for apache and making several virtual http-server for, let me say, test1.os2.local, test2.os2.local, myphpadmin.os2.local. All websites are running on the same ip adress, so i click on the option field "identifying by http headers", and switch of "identifying by ip adress". I close yast, the system tells me that apache will be restartet. All works well. Next time i go to yast again, open the apache setup, go to the virtual server setup ... and all virtual servers are switched back to "identifing by ip adress". So when i save the new setup, from this moment i can enter in my browsers location field either test1.os2.local, test2.os2.local, myphpadmin.os2.local, and the only thing i will see is that apache will show me the same server for all three web pages. I think it is the first that apache finds under the ip adress. Every time i make changes to the virtual server setup, i have to check ALL virtual servers and switch them back to "identifying by http headers" to make them work. greetings from germany (In reply to comment #1 from michal zugec) > Hi Chris, > can you provide me how to "step-by-step" reproduce this problem? > As I understand you mean when you edit already configured one - this is fixed > for 10.3 ... Ok, than this is fixed in 10.3 |