I thing this is due to some misconfiguration on my end but here goes or
My situation is: I am running 1.90 build from a Git clone. I tried to
setup a self-created self-signed cert for a while and could not, server
would not start, do I need to add the CSA ca as well where and how do I
tell yaws to find it.
Finally I found and used the script provided with yaws (yaws/ssl/mkcert)
and got it to start and it has been serving since then but for the
occasional handshake problems in FF (3.x, 7.x), Safari, Konqueror (3.x)
would not even run (very old KDE 3.x when it was the best).
The error in FF reads:
An error occurred during a connection to http://www.nodeunit.com:443.
SSL received an unexpected Handshake record.
(Error code: ssl_error_rx_unexpected_handshake)
I do not have an error log, maybe because I do not have one configured
(am using pretty much the default log from the clone) trying to run the
server in interactive mode with -i and watch the console shows no errors
on the server end when I get the message in Firefox ... any ideas what
to do next??
Another completely unrelated question is how do I enable directory
listing just for one particular directory which I have under basic
authentication but not all of them??
And a third unrelated question: how do I use yaws to accept a connection
contact another server/java container for the response and then forward
that to the client, any sample code? Is that possible?
Thanks in advance.
On 11/09/2011 02:29 PM, Claes Wikstrom wrote:
> On 11/09/2011 11:04 AM, YU wrote:
>> I've compiled and installed yaws 1.91 on opensuse 11.3 on my root directory.
>> I've place the yaws.init script in the /etc/init.d along with the proper
>> permission set to execute only by root.
>> I get a messaged "program not installed" return 5.
>> Next, I type "yaws -i" at the command prompt, I launch firefox, with
>> localhost:80 it works.
>> What can I do to have it boot up at the system level?
>> If I install it on a server, I would like it to boot up when the server boots up.
>> I also created a rclocal(somehow suse does not allow rc.local names) file, the
>> rclocal shows up as enabled in the system level services list, but I still get a
>> return 5 program not installed when I trie to start the service.
>> Any suggestions?
> I have some vague memories including some similar problems with yaws
> not starting properly at boot on some linux host ... some time ago...
> I think it had to something with $HOME not being set or ... maybe
> it was some other environ var ... don't remember. beam just terminated and
> the error went to /dev/null or someting ...
> Try to modify the /etc/init.d/yaws script to to env to /tmp/env,
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> Erlyaws-list mailing list