kswan wrote:
An easy way to create and remove the symlinks in /etc/apache2/mods-
enabled and /etc/apache2/sites-enabled is to use the commands:
a2enmod Enables a module
a2dismod Disables a module
a2ensite Enables a site
a2dissite Disables a site
For example use 'sudo a2enmod rewrite' to enable mod_rewrite.
These commands depend on the modules or sites already existing in the
mods-available and sites-available.
Thanks to all the kind assistance that has been sent my way.
Regrettably, I still have no success. Progress, yes.
I had earlier learned about the a2enmod enabling modules and I have so
done. Just did come to understand a2ensite and how that creates the
symlinks in sites-enabled. May it amuse you to know that many folks
told me just to hack the ProxyPass into sites-enabled/000-default. FAIL!
Where I am now, the ProxyPass is being recognized. Since the package I
am trying to link to uses https, I even went through the whole
unrecognized certificate "red alert" crap that Firefox throws up now.
But then I see "Connecting to 10.10.1.2" in the lower left had corner of
the Firefox screen. 10.10.1.2 is the local address of the machine
_behind_ the proxy. Why am I seeing that on the public side???
Eventually the browser times out as the private IP cannot come back
(guessing) for all manner of routing reasons.
Here are snippets from the "mysite-ssl" file I building
ProxyRequests Off
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
ProxyPass /mysite https://10.10.1.2
ProxyPassReverse /mysite https://10.10.1.2
There is something real obvious that I am missing.
Howard
--
You received this message because you are subscribed to the Google Groups
"NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nlug-talk?hl=en
