jimp
09-13-2006, 03:07 PM
NodeWorx appears to be blindly parsing for the term "SSL" in the domain's Apache configuration.
Steps
Open a domain's Apache configuration for editing.
Add a comment with the word "SSL" in it.
Ex: # Force SSL if the request is for secure.domain.com.
Do something with InterWorx-CP that causes an edit in the Apache configuration.
Ex: Add a SSL certificate.After step #3, the Apache server is completely stopped because a parse error now exists in the domain's configuration.
Before
# Force SSL if the request is for secure.domain.com. After
SSL if the request is for secure.domain.com.Workaround
Avoid the term "SSL" in comments.
# Force S.S.L if the request is for secure.domain.com.
Steps
Open a domain's Apache configuration for editing.
Add a comment with the word "SSL" in it.
Ex: # Force SSL if the request is for secure.domain.com.
Do something with InterWorx-CP that causes an edit in the Apache configuration.
Ex: Add a SSL certificate.After step #3, the Apache server is completely stopped because a parse error now exists in the domain's configuration.
Before
# Force SSL if the request is for secure.domain.com. After
SSL if the request is for secure.domain.com.Workaround
Avoid the term "SSL" in comments.
# Force S.S.L if the request is for secure.domain.com.