Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • HTTPS does not expose the url, only the ip and port. Commented Jun 24, 2014 at 14:56
  • @Daenyth sorry, my knowledge is sorely lacking on the web [development] side, what do you mean httpS doesn't expose the url? Doesn't the request go through (when checking Fiddler, or something like that) like it's displayed above? Commented Jun 24, 2014 at 14:59
  • You can see it locally because you made the request and can decrypt it. HTTP is completely wrapped in SSL, they're at different network layers. However due to server logging urls and client side browser caching it's probably still good practice to hide them. Commented Jun 24, 2014 at 15:01
  • Why are you putting user/pass in the url if you are sending HTTP Basic auth headers? Commented Jun 24, 2014 at 15:48
  • 1
    You should fix the bug causing the hang instead of using two auth schemes like that Commented Jun 24, 2014 at 18:13