Adding documentation for how to issue curl requests

[arschles]

This PR adds instructions to the end of the walkthrough.md documentation that explain how to issue curl requests to your newly created application. Thanks to @iompo for the suggestion in #335 (reply in thread) to add this documentation

Checklist

• Commits are signed with Developer Certificate of Origin (DCO)
• Any necessary documentation is added, such as:
  • README.md
  • The docs/ directory
  • The docs repo

@iompo can you let me know if this documentation makes sense?

[iompo]

Hi @arschles, I think it does.
By the way, I know it's not connected to your changes, but in the "Creating an HTTPScaledObject" section there's something missing in this sentence: "This CRD object points the To get an example app up and running".

[tomkerkhove]

Hi @arschles, I think it does. By the way, I know it's not connected to your changes, but in the "Creating an HTTPScaledObject" section there's something missing in this sentence: "This CRD object points the To get an example app up and running".

Great remark @iompo, are you open to send a PR?

[iompo]

Hi @tomkerkhove, yes I can do that.

[iompo]

Hi @arschles, I just realized that, in the part of the doc you just added, there's one thing I did not fully understand: there's a note about the Host header, you say that "If you have a DNS name set up for the IP, you don't need this header". Without that header how can the keda-add-ons-http-interceptor-proxy know to what service redirect the request?

[arschles]

@iompo that is because the interceptor looks at both the Host header and the actual host in the incoming request URL. If you issue a request to myhost.com, the interceptor will detect the intended target app from the request URL's host