Hi Everyone,

I'm still wondering how to get PHP working on port 8443, so that I can run PHP and MYSQL alongside Galene. (e.g. https://www.servername.com:8443/test.php)

Is this query beyond the scope of this group, and more of an Apache configuration issue?

As you can tell there is a gap in my knowledge of this kind of architecture but from my testing, I definitely cannot have a host php page running on port 80 that attempts to create the websocket for Galene over on port 8443 via javascript. That definitely doesn't work, and therefore, for a successful Galene connection, I need to use an https uri request on port 8443, before the javascript makes the wss connection.

This means therefore, for my design to work, I need PHP to run on port 8443.

Any ideas how to get PHP running on port 8443?

Hopefully we can forge an answer although I realise this is slightly leftfield to the amazing development of core Galène that you're all working on.

Best wishes and kind regards,
Rob

On Tue, 2 Mar 2021 at 18:37, Juliusz Chroboczek <jch@irif.fr> wrote:

> I was wondering if it were possible to use Galčne inside a PHP page, as we want
> to get our students to fill out some details before joining in, and we thought
> that we could use php SESSION cookies to check they've completed everything
> before letting them in.

Sure. What you'll want to do depends on your security model, though.

The simplest, but least secure, would be to check your session cookie in
the galene.js file; look around line 2600, where it says

document.getElementById('userform').onsubmit

This is easily gamed by the user (they can edit the source code in the
browser), but if the goal is simply to guide the students and has no
influence on their grades, it's probably good enough.

If, on the other hand, you want stronger security, you'll need to pass the
session cookie to the server and do the validation there. You'll need to
add a parameter to the serverConnect.join method, pass the value within
the "value" field of the join message, and do the validation in the function
handleClientMessage in webclient.go.

-- Juliusz