Wie können wir helfen?

z.B. Gantt-Diagramm, Aufgaben erstellen, Ordner teilen

[Resolved] Why does webhooks get suspended (.net Webapi) and request received 3 times.

4 Kommentare

  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Pavel M

    (Bearbeitet )

    Francis, thank you for your post and congrats on being the first contributor to our API community!

    This is a great tip, I am sure many API users will find it useful. Your feedback came just in time! We plan on updating the documentation on webhooks soon, and we agree that these points should be reflected in our help docs.

    Our engineers may also consider accepting the 204 status code and at this point it would be great to hear your thoughts about it: what is your personal opinion on the necessity of this? We assume that your .Net library defaults to 204, do you feel like accepting only the 200 code would be a serious limitation?

    Pavel M Community Team at Wrike 💡Erfahren Sie mehr über Wrikes leistungsstarke Funktionen und lernen Sie Anwendungsbeispiele kennen

    Is this helpful? 1
    Aktionen für Kommentare Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Francis Mercier

    Thank you. 

    A serious limitation (or even a limitation), definitely not. 

    By default, 204 response means the server has fulfilled the request but does not need to return an entity-body.
    Since payload sent does not except a body returned to it and also that Microsoft developped their .net webapi POST handle to use that response as default behavior, I would be inclined to think that it could be good to accept by default 204 response too. 

    (Please note that "my .net library" was actually Microsoft sample project with nothing custom at all. I did not choose the 204 response for the post request myself, their implementation defines it as the default response for Post request)

    However, that being said and even though I could not find any evidence to not use it as a valid response, I do not see any problem complying to the 200 status response needed at this time. 

     

    Is this helpful? 0
    Aktionen für Kommentare Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Pavel M

    Thank you for your feedback, Francis! This definitely makes sense, we will discuss the possibilities of avoiding such limitations in the future.

    Pavel M Community Team at Wrike 💡Erfahren Sie mehr über Wrikes leistungsstarke Funktionen und lernen Sie Anwendungsbeispiele kennen

    Is this helpful? 0
    Aktionen für Kommentare Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Pavel M

    (Bearbeitet )

    Francis, we have great news - our engineers have released the update to Webhooks, which allows Wrike's API to accept the 204 status code.

    Anyways, I wanted to thank you again for your workaround and contribution to the Community. What you proposed was an easy and elegant way to avoid the limitation!

    Pavel M Community Team at Wrike 💡Erfahren Sie mehr über Wrikes leistungsstarke Funktionen und lernen Sie Anwendungsbeispiele kennen

    Is this helpful? 0
    Aktionen für Kommentare Permalink

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

Folllowing List for Post: [Resolved] Why does webhooks get suspended (.net Webapi) and request received 3 times.
[this list is visible for admins and agents only]

Community

Welcome 🖖

Hi there! 🙂 Want to become a black belt Wrike Ninja? Here's how to earn a Wrike badge

Welcome 🖖 Have you checked out this week's Release Notes yet?

Hey! 👋 Curious about something? Visit How To to search and ask the Community for answers.

Welcome! 👋 Figured out a good tip or trick? Share it in Best Practices.

Want to connect your existing software to Wrike? Learn and ask how in the API section.