If HTTP post makes "cookie based authentication" mandatory, then nanohttp does not handle this as there is no key called Cookie. Even if we add Cookie key, the value of it must be the one sent in HTTP header sent by the server. So we cannot have a dummy username::password value.
I have a fix for this issue.
Can anyone tell me where to upload the changes so that in can be included in further nanohttp releases after review
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.