Reputation
374
Top tag
Next privilege 500 Rep.
Access review queues
Badges
2 7
Newest
 Commentator
Impact
~34k people reached

  • 0 posts edited
  • 0 helpful flags
  • 2 votes cast
12h
answered Not able to restrict the user to particular directory in unix
15h
awarded  Commentator
15h
comment Apache's deprecated SSLCertificateChainFile directive (AH02559)
Building the chain is not trivial for a novice, i guess. I usually run openssl x509 -subject -issuer -noout -in certificate.of.yourdomain.crt to see the issuer. I then download the issuing certificate from the website of my CA, in your case: startssl.com/certs. Then run the command on that certificate. Repeat until issue equals subject, which means the certificate is self-signed, and is the root CA certificate. add all those files except root CA cert to the ssl.crt and your done.
16h
comment Nginx Load Balancing proxy confusion
With the redierct scenario, no it won't affect throughput. It will result in overheader in the sense that the client will make 2 request. 1) to nginx, which will tell the client to go look for the file in a different place. 2) the actual file download from box1X.example.com
17h
comment Solr / Jetty install hangs running java -jar start.jar
When you reboot the server? As in shutdown -r/init 6? Can you check if SOLR is even running after rebooting your server?
17h
revised Apache's deprecated SSLCertificateChainFile directive (AH02559)
Clarified chain enumeration.
17h
comment Apache's deprecated SSLCertificateChainFile directive (AH02559)
That depends on the actual chain, i mean the number of CAs involved in signing your certificate. The chain may only consist of 2 CAs. e.g. Root CA and one intermediate CA. But it may consist of Root CA and more than one intermediate CA. Your ssl.crt file should contain all intermediate CA certificates, from top to bottom. For this reason, it absolutely depends on you specific case how your ssl.crt should look like.
17h
answered Apache's deprecated SSLCertificateChainFile directive (AH02559)
18h
comment How to log uploaded files with nginx?
That's right. For nginx it's just an incoming request body. Nginx has no concept of what "type" of data the request body contains. It can't tell whether the webapp your nginx is forwarding these requests to is handling the request body as form data, or a file upload... the only thing that will happen in nginx is that the request body will be written to disk if it's too large for it's internal buffers.
18h
comment Nginx Load Balancing proxy confusion
The answer to the redirect question you linked will actually tell the client to download the file directly from box1X.example.com.
May
30
awarded  Notable Question
Jul
20
awarded  Yearling
Jul
20
answered Close a process without psKill and force?
Jun
16
awarded  Supporter
Apr
8
awarded  Popular Question
Nov
8
answered How to mount a shared folder in Windows Server 2008?
Nov
8
answered Change last logon for user(s) in Active Directory
Nov
8
comment Unable to mount samba shares
budde: that's what i was thinking too, because of the ">" in "cmd > ~:...." which usually indicates the shell running as non-root user
Nov
7
awarded  Editor
Nov
7
revised My software RAID is all screwed up
added 169 characters in body