Re: [naviserver-devel] What's the replacement of [curl -u] in [ns_http]

2021-02-23 Thread Iuri de Araujo Sampaio
Hi everyone, So far, It seems ns_base64encode generates a different hash key, and the colon is the problem somehow. A valid request from Postman or CURL, has the following Authorization block within it : Authorization {Basic HGTRFHTYhththtyhotyhtyjotjytjojg956456346n64ui5n4436346nu4y4iuyn4

Re: [naviserver-devel] What's the replacement of [curl -u] in [ns_http]

2021-02-23 Thread Gustaf Neumann
Dear Iuri, The problem, you are probably facing is probably that ns_base64encode produces line breaks as required for MIME encoded text strings [1]. % ns_base64encode Afrewf564DFSFSF54jgnfhgGDGdfRGRT43:7584fjhfjhf84jkrugrefAFFD9449474 QWZyZXdmNTY0REZTRlNGNTRqZ25maGdHREdkZlJHUlQ0Mzo3NTg0ZmpoZ