1. 30 Apr, 2013 2 commits
  2. 29 Apr, 2013 1 commit
  3. 27 Apr, 2013 1 commit
    • Stratos Psomadakis's avatar
      Suggest running vncauthproxy as nobody:www-data · b1ea672c
      Stratos Psomadakis authored
      Running vncauthproxy as nobody:www-data makes more sense. We have better
      privilege separation between apache2/gunicorn and vncauthproxy, while
      gunicorn can still to connect to the vncauthproxy's control socket.
      When/if vncauthproxy starts using TCP ctrl sockets instead of UNIX, this
      could be omitted entirely.
      We could also consider adding a separate user/group for vncauhtproxy.
  4. 26 Apr, 2013 3 commits
  5. 25 Apr, 2013 2 commits
  6. 23 Apr, 2013 5 commits
  7. 22 Apr, 2013 16 commits
  8. 19 Apr, 2013 1 commit
    • Olga Brani's avatar
      Astakos: ui minor fixes · d4875b66
      Olga Brani authored
      Refs: #3573 
      Correct onclick functionality in project create page.
      Discover missing div tag in project details page.
  9. 18 Apr, 2013 3 commits
  10. 17 Apr, 2013 4 commits
  11. 16 Apr, 2013 2 commits
    • Sofia Papagiannaki's avatar
      pithos: Change conflict handling in object write · ab73ab61
      Sofia Papagiannaki authored
      Pithos in case of missing blocks during smart object write
      (using hashmap) used to raise an api fault with payload
      the list with the missing blocks serialized in json format.
      However, the common api_method decorator in case of api fault
      returns a different response content format containing details about
      the fault.
      This causes problem to pithos clients which expect
      a specific response content format in that case.
      The solution was adopted is:
      when pithos server detects such a case returns directly
      an HttpResponse with the same status code (409) as before
      and the expected content.
    • Christos Stavrakakis's avatar
      Fix API decorator response Content-Type · 3b538afa
      Christos Stavrakakis authored
      Remove check for response Content-Type, since 'django.http.HttpResponse'
      has always a default Content-Type of 'text/html; charset=utf-8'. Views
      defining their response 'Content-Type' should set the
      'override_serialization' attribute of response to 'True'.