Grid and HTTPS

[Steve Zaluk]

We are seeing an issue when we are running the Grid with default
options and using a ProxyPass directive in Apache to route it through
HTTPS. When we try to register the nodes, we are using the following:

java -jar selenium-server-standalone-2.19.0.jar -role node -hub https:/
servername/grid/register -browser
browserName=firefox,version=10,maxInstances=5,platform=WINDOWS

This is the output we are seeing when the nodes try to register:

17:51:11.803 INFO - starting auto register thread. Will try to
register every 5000 ms.
17:51:11.803 INFO - Registering the node to hub :http://servername:-1/
grid/register
17:51:11.974 INFO - couldn't register this node : Error sending the
registration request.

Any idea why the URL is being converted from https to http and a -1 is
being inserted as the port number? We are using Selenium 2.19.

Thanks,
Steve

[Santiago Suarez Ordoñez]

Hm, does registering over http actually work? Probably Kevin or Francois are the ones to answer here.

Santi

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To post to this group, send email to selenium-...@googlegroups.com.
To unsubscribe from this group, send email to selenium-develo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/selenium-developers?hl=en.

[Kevin Menard]

Your port shouldn't be -1. Have you done something funky on the node
end where you're overriding the port value improperly?

--
Kevin

[Steve Zaluk]

Hey Guys,

Any thoughts on this? We can run our tests against the Grid running
this way but we have to register the nodes on HTTP or they won't
register. I normally wouldn't care about this and run it under HTTP
but we have strict rules about what ports can be open here and IT
wants all traffic to go over HTTPS.

Thanks,
Steve

[Steve Zaluk]

Yes. I can still register them using the defaults,
http://servername:4444/..... The issue seems that when I do specify
https, it gets converted to http and a -1 is added as the port number.

[Kevin Menard]

Oh, gotcha. I'm pretty sure it just doesn't speak HTTPS. I'll
double-check, but if you need something today, your best bet is
probably to use stunnel or SSH port forwarding to relay HTTP over a
secure channel.

--
Kevin

[Steve Zaluk]

Ok, thanks. We also use the Grid for our iPhone and Android web
tests. Is there anything I can do to get that working?

Do we ever plan on supporting HTTPS in the future?

Thanks for the help,
Steve

[Steve Zaluk]

No, not at all. I am starting the node up just like this:

java -jar selenium-server-standalone-2.19.0.jar -role node -hub

https://servername/grid/register -browser
browserName=firefox,version=10,maxInstances=5,platform=WINDOWS

And this is what I am seeing when it tries to register:

17:51:11.803 INFO - Registering the node to hub
:http://servername:-1/grid/register

If I change that above statement to start the node to the following it
works fine:

java -jar selenium-server-standalone-2.19.0.jar -role node -hub

http://servername:4444/grid/register -browser
browserName=firefox,version=10,maxInstances=5,platform=WINDOWS

I am starting the hub as follows:

java -jar selenium-server-standalone-2.19.0.jar -role hub

We setup ProxyPass on the hub server so all requests go through HTTPS.
If I start up the nodes using 4444 in the second example, I can run
tests through our grid using https://servername/wd/hub so I know that
is working. The problem is just when I try to register the nodes
against https.

Thanks,
Steve

[Kevin Menard]

I don't want to say we'll never support SSL, but it seems like a bit
of a stretch. The Selenium server itself doesn't bind to an SSL
socket, so there's never been a need for the clients to support it.
So, you have the proverbial chicken and egg problem. Since you really
should only be using Selenium server on secured networks to begin
with, I don't see much incentive to add the additional overhead of SSL
on the server side. And without the server support, it's hard to
justify the work in the clients supporting it.

--
Kevin

[Steve Zaluk]

Totally makes sense. The IT department here is overly cautious so we
have no choice.

Thanks for the input!

--Steve