-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Shawn,

On 4/15/18 4:33 PM, Shawn Heisey wrote:
> On 4/15/2018 2:24 PM, Christopher Schultz wrote:
>> No, it wouldn't have. It doesn't read any configuration files
>> and guesses its way through everything. Simply adding HTTPS
>> support required me to modify the script and manually-specify the
>> URL. That's why I went through the trouble of explaining so in my
>> initial post.
> 
> Gotcha.  I haven't used SSL with Solr myself.  Nobody can get
> directly to the Solr servers, so we don't need it.  If somebody is
> able to penetrate our systems to the point where they can sniff
> Solr traffic, they will already have full access to things far more
> sensitive than our search index.

Not necessarily, but that depends entirely upon your environment. We
have a policy of "no privileged network positions" so we don't even
trust our "private networks". Someone at the data center could
inadvertently configure a switch port to suddenly join our VLAN or a
network plug might be incorrectly assigned, etc. So we don't want our
data flying around in a way that can be intercepted.

> I'll see what I can do about the documentation to make it clear
> that the URL given to the post tool needs the request handler
> path.

That would be great. Even poking-around in the Solr web UI doesn't
reveal that path because of all the javascript magic in the interface.

It's unreasonable to expect everyone to read source code in order to
learn how to use tools that don't require direct programming.

Let me take a step back and say that Solr in fact has great
documentation. There are evidently some things it lacks for the
uninitiated.

Thanks,
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlrUn5wACgkQHPApP6U8
pFiN+hAAyyO69VE5ZLGFTk4ti2a4L2+Cvtgdag9GYIvUbX72Zhdwlu2OWBSLVbix
Ibx6XNYKfv88IFzYWrFhTQmPS7Ce35H5Wss2YNfSnGZBhbSrifkCDam06zFZlesH
HTSwrBFs32rTB41c4d6WrBR1wgSOirRsIQ4iDitoIRcGhDsdn3y4nANqoSp3/ZmM
hYJEZ57pa7+aon4hbXde5aYKs5NGqkvOg0XAvctscDSPifZ9sijOgwM7DmABoqit
9oUB5s9pvOt0eA1czhI+gAvgscXdReo8A2i2l1hFxGhvaZ0Xnl2OJqjkNSwhUfaB
J9sc/j/LYWSzapBFl6b9fDYAqjxIcwkLtlX/BOOwLzZWa0Gjnj3OkJSfO6pZjtC3
ZQkBC2a8cyBbx3OW7GyyTzCDKQdYceslXiyYvFiqAEJL5u1SpPfbD8l9XdoTRDzL
M+lsmq9NW7ZDDk5VCAzHr6WVrcTGVM9wZPy4lJ+Wi5sOA/VS8QrXP/J+lJg8blID
MhUCstVZHY9MT6NwQxYpfBb/Sc00/sksakhkdSt95GOEnUnz3cxiW/gqaYEq6b6q
LugrqUuLz9Iy+OVPRzIj7dT31JQERpLm1wELcbY0QutI2hPICkIaec5Pw/avdRBW
UmRrESPK7+zOly+j+WVy2noX2+Y6/orje4oP3ETTPRA1Ey4Y2Xs=
=2ntw
-----END PGP SIGNATURE-----

Reply via email to