Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-5674

FIWARE.Question.Tech.Data.CEP.REST consumer stopped working after error and URL invalid charactes

    Details

      Description

      Created question in FIWARE Q/A platform on 15-01-2016 at 12:01
      Please, ANSWER this question AT http://stackoverflow.com/questions/34810337/fiware-cep-proton-rest-consumer-sto-working-after-error-and-url-invalid-charac

      Question:
      FIWARE CEP (Proton) REST consumer sto working after error and URL invalid charactes

      Description:
      I'va noticed that if the requests send via REST consumer return an error (invalid scheme, connection refused, error 400, etc.) the REST consumer doesn't work anymore. To get it back, I had to reload the definition file.
      I think that this may be a bug.

      Moreover, during these tests, I've also noticed that not all the URL were accepted. For example, by omitting the "http://" Proton returns "invalid scheme" error. Whereas, URL with "-" isn't parsed correctly and the "connection refused" error is returned.
      It'd very helpful to have a list of prohibited characters.

      Thanks.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        2d 19h 36m 1 Fabiana Fournier 18/Jan/16 10:39 AM
        In Progress In Progress Answered Answered
        5s 1 Fabiana Fournier 18/Jan/16 10:39 AM
        Answered Answered Closed Closed
        1m 27s 1 Fabiana Fournier 18/Jan/16 10:41 AM
        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        mev Manuel Escriche made changes -
        HD-Enabler CEP [ 10869 ]
        HD-Chapter Data [ 10838 ]
        TALI Fabiana Fournier made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        TALI Fabiana Fournier made changes -
        Summary [fiware-stackoverflow] FIWARE CEP (Proton) REST consumer sto working after error and URL invalid charactes FIWARE.Question.Tech.Data.CEP.REST consumer stopped working after error and URL invalid charactes
        TALI Fabiana Fournier made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        TALI Fabiana Fournier made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Hide
        TALI Fabiana Fournier added a comment - - edited

        The Stackoverflow entry was not a question, but rather request to check if a certain behaviour is a bug and to publish what are the invalid characters in the CEP REST URL.

        I opened two bugs in Jira to cover it:
        FIWARE.Bug.Data.CEP.Rest.ListOfInvalidURLCharacters,
        FIWARE.Bug.Data.CEP.Rest.ConsumerStoppedWorkingAfterInvalidCall

        I added a comment to the Stackoverflow entry to document it.

        Show
        TALI Fabiana Fournier added a comment - - edited The Stackoverflow entry was not a question, but rather request to check if a certain behaviour is a bug and to publish what are the invalid characters in the CEP REST URL. I opened two bugs in Jira to cover it: FIWARE.Bug.Data.CEP.Rest.ListOfInvalidURLCharacters , FIWARE.Bug.Data.CEP.Rest.ConsumerStoppedWorkingAfterInvalidCall I added a comment to the Stackoverflow entry to document it.
        mev Manuel Escriche made changes -
        Assignee Tali Yatzkar Haham [ tali ]
        backlogmanager Backlog Manager made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        Hide
        backlogmanager Backlog Manager added a comment -

        2016-01-15 15:05|CREATED monitor | # answers= 0, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2016-01-15 15:05|CREATED monitor | # answers= 0, accepted answer= False
        backlogmanager Backlog Manager created issue -

          People

          • Assignee:
            TALI Fabiana Fournier
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: