none
WNS service is resetting connection when sending notification to channel URI RRS feed

  • Question

  • Hi,

     

    we have a notification service up and running for several years now, that uses WNS to send push (toast) notifications to our Windows UWP App. Recently however, we are not able to send notifications from our backend anymore.

     

    It seems to us that our server has been blocked, because as soon as we send POST requests to a channel URI, our connection is being closed by the remote host (we are not even getting a response from WNS).

     

    The only part that does still work is obtaining the access token for our app. We haven't changed anything in our configuration, neither on the app or on the server. We also know that there is no issue within our backend logic, as our test server on another location (which is a clone of our live server) can send notifications to the same channel URI's without any issue.

     

    Has anyone faced a similar issue like that before ? We could understand, if we would have reached certain limits (f.e. by sending an unusual large amount of notifications) but we have an average of ~1500 notifications to WNS in total per day, which is hardly enough to cause this.

    Those are the headers / content of our POST request:

    Content-Type: text/xml
    X-WNS-Type: wns/toast
    Authorization: Bearer <our access token>
    
    <toast>
    <visual>
    <binding template="ToastText01">
    <text id="1">some text</text>
    </binding>
    </visual>
    </toast>







    • Edited by IDGH Thursday, August 6, 2020 11:00 AM
    Thursday, August 6, 2020 10:31 AM

Answers

  • Hello Bryan,

    thanks for the reply. We have solved the issue by moving our push service to another location. If this happens again, I will post it to the forum mentioned.

    • Marked as answer by IDGH Wednesday, August 12, 2020 5:31 PM
    Wednesday, August 12, 2020 5:31 PM

All replies

  • Hi IDGH,

    The purpose of this forum is to assist folks that are implementing one of Microsoft's protocols in a third-party implementation.  The protocols are enumerated at https://docs.microsoft.com/en-us/openspecs/protocols/ms-protocolslp/9a3ae8a2-02e5-4d05-874a-b3551405d8f9.  Are you implementing a protocol and interoperating between a Microsoft platform and a platform of your own creation?


    Bryan S. Burgin Senior Escalation Engineer Microsoft Protocol Open Specifications Team

    Thursday, August 6, 2020 7:23 PM
    Moderator
  • Hi Bryan,

    in fact we do, we have our own implementation to communicate with WNS (we do not use solutions like Azure Notification Hub). But this post would probably be more suitable in the Windows and Windows phone apps > Developing Universal Windows apps sub forum, however when submitting this question I was not able to select this forum, so I posted it here.

    If it does not fit in here, please move it to the mentioned sub forum.


    • Edited by IDGH Friday, August 7, 2020 7:01 AM
    Friday, August 7, 2020 7:01 AM
  • Please try to post your question to the WNS forum at https://docs.microsoft.com/en-us/answers/topics/windows-uwp.html


    Bryan S. Burgin Senior Escalation Engineer Microsoft Protocol Open Specifications Team

    Tuesday, August 11, 2020 5:57 PM
    Moderator
  • Hello Bryan,

    thanks for the reply. We have solved the issue by moving our push service to another location. If this happens again, I will post it to the forum mentioned.

    • Marked as answer by IDGH Wednesday, August 12, 2020 5:31 PM
    Wednesday, August 12, 2020 5:31 PM