|
Apr
30 |
|
awarded | Notable Question |
|
Apr
21 |
|
awarded | Popular Question |
|
Apr
18 |
|
comment |
C++: Implementing merge sort from scratch Thanks so much for the perfect answer and thanks for solving it in the way I wanted it to be solved. |
|
Apr
18 |
|
accepted | C++: Implementing merge sort from scratch |
|
Apr
17 |
|
asked | C++: Implementing merge sort from scratch |
|
Apr
9 |
|
awarded | Popular Question |
|
Apr
4 |
|
awarded | Popular Question |
|
Apr
2 |
|
awarded | Popular Question |
|
Mar
25 |
|
awarded | Notable Question |
|
Mar
18 |
|
awarded | Popular Question |
|
Feb
27 |
|
awarded | Popular Question |
|
Feb
21 |
|
awarded | Custodian |
|
Feb
21 |
|
reviewed | Approve suggested edit on Nginx routing to another site |
|
Feb
21 |
|
comment |
Nginx routing to another site I have a problem with the JSON data sending. I did not understand why but the JSON data is not being conceived by the b.com |
|
Feb
21 |
|
awarded | Supporter |
|
Feb
21 |
|
comment |
Nginx routing to another site In the conf I have there is http {} defined. Should I delete it and later on add the server {} ? |
|
Feb
21 |
|
asked | Nginx routing to another site |
|
Feb
12 |
|
comment |
Implementing one time keys efficiently @TheBronx Yes, I guess there is nothing to do after that |
|
Feb
12 |
|
comment |
Implementing one time keys efficiently @CodesInChaos Is it wise to trust only a single layer (even though its SLL) and not to another layer of security? |
|
Feb
12 |
|
comment |
Implementing one time keys efficiently @CodesInChaos We will be using SLL. What we are trying to do is that even the data package is captured once we won't let the attacker to be able to use the secretKey again to perform a "fake request" and use our system as an authorized user |
