This is part 3 of a series of blog posts in which I walk through the creation of a simple chat app with Solace PubSub+. In the first part, I explained how to create a simple chat app that can send and receive messages via a direct topic subscription. In the second I explained how to modify the sample code so the application consumes messages from a queue. In this part, I’ll explain how to send a REST POST request from a login page to a dummy authentication service fronted by Solace PubSub+.

Specifically, you will:

  • Add a server URL
  • Complete fetch parameters



  • Beginner

Add a Server URL

By adding a server URL, you define where the REST POST request is sent to. To add a server URL, do the following:

  1. In your code editor, check out the developer-exercise-3 branch or in your command line, enter git checkout remotes/origin/developer-exercise-3 -f
  2. Open the solaceauth.js file under src > main > resources > static > scripts Open the solaceauth.js
  3. Enter the highlighted code to add the server URL (Line 15).
    //Enter serverUrl
    var serverUrl = ‘http://localhost:8081/solace/cloud/proxy’,

    This URL sends the request through our web application server, which sends it to our Solace instance.

Complete Fetch Parameters

The fetch method defines how information is obtained from the server. Do the following to add the method and headers parameters:

  1. Enter the highlighted code to add POST as the method (Lines 22-23).
    //Complete fetch parameters; method and headers
    fetch(serverUrl, {
       method: “POST”,
  2. Under the above code, enter the highlighted code to set the content-type of the request header (Lines 24-25).
    headers: {
       “Content-Type”: “application/json; charset=utf-8”,

    This tells the receiving server to deal with the REST message content in JSON format with the UTF-8 character encoding.

  3. In your code editor, type mvn spring-boot:run to run the application.
  4. In your Web browser, enter localhost:8081 to see the login page.
  5. Type any username and password. You should get a “Login Failed” message.

    This is because we have just sent the REST POST request to the Solace instance and have not yet set up the login server. We will do that in the next tutorial.


You have added login functionalities to the Web application to send a REST POST request to Solace PubSub+.

In the next part of the series, you will learn how to add a simple authentication server.


Hong Qiu
Hong Qiu

Hong is the Senior Community Manager at Solace, where he is responsible for building and managing the Solace community and creating developer-focused content. Prior to Solace, he spent over 10 years at Adobe managing the Adobe Developer Connection portals and planning, creating, and sourcing content for them. Before Adobe, he was a senior technical writer at Nortel and a technical writer at Cognos (now IBM).