Opush
  1. Opush
  2. OP-85

T#10719 Check why opush returns HTTP 401 when there's a SQL error in obm-sync

    Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Normal Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.0.2
    • Labels:
    • Story Points:
      2
    • Rank:
      6398
    • Sprint:
      Sprint

      Activity

      Show
      Stephane COLSON added a comment - https://wiki.linagora.com/obm//QA/DefinitionOfDone#4._A_rajouter_en_commentaire_avant_de_pousser_le_ticket_en_RTM please
      Hide
      Stephen LE MAISTRE added a comment -

      Impacts

      Now runtime errors which could occur when a smartphone is trying to authenticate returns 500 instead of 401.

      Tests done

      No tests done. It's hard to reproduce the Tosca (+ no devices available).

      Show
      Stephen LE MAISTRE added a comment - Impacts Now runtime errors which could occur when a smartphone is trying to authenticate returns 500 instead of 401. Tests done No tests done. It's hard to reproduce the Tosca (+ no devices available).
      Hide
      Antoine DUPRAT added a comment -

      OK with version 3.0.2~beta3~git20141009.091827.60ca887-1

      Tested on Debian Wheezy 3.2.46-1+deb7u1

      Reproduced when shuting down obm-sync and try to synchronize.

      Show
      Antoine DUPRAT added a comment - OK with version 3.0.2~beta3~git20141009.091827.60ca887-1 Tested on Debian Wheezy 3.2.46-1+deb7u1 Reproduced when shuting down obm-sync and try to synchronize.

        People

        • Assignee:
          Stephen LE MAISTRE
          Reporter:
          David Dolcimascolo
        • Votes:
          0 Vote for this issue
          Watchers:
          4 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:

            Agile