On Tue, 17 Nov 2015, kcrisman wrote:
Jori, are you using Jonathan Gutow's branch for proxying?
No.
I rearranged things. We have now a) redirection http://sage.our.unit ->
https://sage.our.unit and b) documentation online at
http://sage-doc.our.unit.
This seems to now work. Apache is used
Jori, are you using Jonathan Gutow's branch for proxying? If so, that
would be great - I hope to work on sagenb updating later today.
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from
On Fri, 13 Nov 2015, Jori Mantysalo wrote:
RewriteRule ^(.*)$ http://localhost:1234/$1 [P]
Now I was able to delete this and everything almost work.
I have static documentation available without login at port 80. Server is
at 443 so that Sage listens port 8000 and Apache configuration have
On Thu, 12 Nov 2015, Gutow, Jonathan H wrote:
I strongly recommend using a frontend like ngix or Apache. The
efficiency of the Sagenb server when doing encryption is low. Let an
industrial strength web server handle that and the encryption.
Speed is not a bottleneck for me, but anyways, I'l
On Thu, 12 Nov 2015, Karl-Dieter Crisman wrote:
Without proxying on a local machine sagenb just launches. The only
difference is that it is now at http://localhost:8080/sage/.
Would the same be true for a non-proxied launch to the internet? (Assuming one
did such a thing.)
Yes. I have done
> Without proxying on a local machine sagenb just launches. The only
> difference is that it is now at http://localhost:8080/sage/.
>
>
>
Would the same be true for a non-proxied launch to the internet? (Assuming
one did such a thing.)
--
You received this message because you are subscribed to t
> On Nov 12, 2015, at 10:15 AM, Karl-Dieter Crisman wrote:
>
>
>
>
> I strongly recommend using a frontend like ngix or Apache. The efficiency of
> the Sagenb server when doing encryption is low. Let an industrial strength
> web server handle that and the encryption. I just proxy a local
I strongly recommend using a frontend like ngix or Apache. The efficiency
> of the Sagenb server when doing encryption is low. Let an industrial
> strength web server handle that and the encryption. I just proxy a local
> instance of the Sagenb behind Apache when I want a secure connection and
>
I strongly recommend using a frontend like ngix or Apache. The efficiency of
the Sagenb server when doing encryption is low. Let an industrial strength web
server handle that and the encryption. I just proxy a local instance of the
Sagenb behind Apache when I want a secure connection and then
On Thu, 12 Nov 2015, Michael Orlitzky wrote:
Can Sagenb send certificate chain instead of just certificate of the
server itself? If yes, how?
You can probably just concatenate the certificate files. Something like,
$ cat www.example.com.crt intermediate.pem > combined.crt
Tested, b
On 11/12/2015 12:00 AM, kcrisman wrote:
>
> Can Sagenb send certificate chain instead of just certificate of the
> server itself? If yes, how?
>
> If not, what do you use as a frontend? Apache?
>
>
> Cc:ing someone who may know this; I don't know anything about the
> certificates.
>
On Wed, 11 Nov 2015, Jori Mantysalo wrote:
If not, what do you use as a frontend? Apache?
Apache seems to work, I was able to log in and saw my worksheet and
plot() worked. However, logout sent me to localhost. So not all links work
-- maybe there are more that do not work.
Suggestions wel
> Can Sagenb send certificate chain instead of just certificate of the
> server itself? If yes, how?
>
> If not, what do you use as a frontend? Apache?
>
>
Cc:ing someone who may know this; I don't know anything about the
certificates.
--
You received this message because you are subscrib
13 matches
Mail list logo
