Skip to content
  1. Nov 02, 2016
  2. Oct 10, 2016
    • Vladimir Homutov's avatar
      Merge pull request #10 from rysiekpl/master · 40fc2ef2
      Vladimir Homutov authored
      Minor bugfixes
      40fc2ef2
    • Michał 'rysiek' Woźniak's avatar
      Minor bugfixes: password can now contain colons, log_message uses self.ctx... · 24bf24ff
      Michał 'rysiek' Woźniak authored
      Minor bugfixes: password can now contain colons, log_message uses self.ctx (instead of global ctx, which does not exist)
      24bf24ff
    • Vladimir Homutov's avatar
    • Vladimir Homutov's avatar
      Updated documentation and example. · d56a55e2
      Vladimir Homutov authored
      Commit 06444b36 changed returned error
      code from 403 to 401 in case of failed auth and documentaion must be
      updated accordingly.
      d56a55e2
    • Vladimir Homutov's avatar
      Merge pull request #9 from ArfyFR/patch-1 · 06444b36
      Vladimir Homutov authored
      Use RFC2616 recommandation to reply 401 instead on 403 for auth_failed
      06444b36
    • Vladimir Homutov's avatar
      more robust error routine. · 7f3634bb
      Vladimir Homutov authored
      self.ctx may be unset in case of bad request or other low-level error.
      7f3634bb
    • ArfyFR's avatar
      Use RFC2616 recommandation to reply 401 instead on 403 for auth_failed · f57c0538
      ArfyFR authored
      Cf https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html ,
      
      401 is for: auth failed... please retry ;)
      -----------
      10.4.2 401 Unauthorized
       The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field (section 14.8). If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity might include relevant diagnostic information. HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" [43].
      
      
      
      403 is for: more or less auth shouldn't be repeated
      -----------
      10.4.4 403 Forbidden
       The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead.
      
      Regards,
      Pascal
      f57c0538
  3. Jul 08, 2016
  4. Jul 05, 2016
  5. Jun 28, 2016
  6. Jun 22, 2015
  7. Jun 19, 2015
Loading