Golang HTTP GET request returning 404

Question

I am trying to execute a simple HTTP get with BasicAuth. The problem is that the response keeps coming back "404", even though I can copy and paste the URL into a command-line cURL request and it works fine:

const url string = "http://1.2.3.4:6710/REST/command"
const username string = "..."
const password string = "..."

fmt.Printf("\n%v\n", url)

client := &http.Client{}

req, _ := http.NewRequest("GET", url, nil)
req.SetBasicAuth(username, password)
req.Proto = "HTTP/1.0"
req.ProtoMinor = 0

resp, _ := client.Do(req)

fmt.Printf("\n%v\n", resp)

defer resp.Body.Close()
body, _ := ioutil.ReadAll(resp.Body)   

fmt.Printf("\n%v\n\n", string(body))

So you can see that I am printing out my url immediately - this is the same line of text that if I copy into a command-line cURL request, all works perfectly.

My request response is

&{404 Not Found 404 HTTP/1.0 1 0 map[Pragma:[no-cache] Date:[Wed, 17 Apr 2013 15:01:33 GMT] Connection:[close] Server:[MoneyWorks_Datacentre/6.1.3 Win-x86 REST/6.1.3] Cache-Control:[no-store, no-cache, must-revalidate] Expires:[Wed, 17 Apr 2013 15:01:33 GMT]] 0xf8400e3920 -1 [] true map[] 0xf8400aa000}

Is there anything unique to golang's HTTP functions that differ from the way cURL would handle such a simple request?

EDIT: I have it working by passing the URL to exec.Command("curl", url).Output(). Obviously this is not the native solution I am hoping for but it works for now.

I tried your example above on a web page which needs authentication and it worked fine. The moneyworks docs are worth a read, re HTTP/1.0. I don't see your auth parameters for your curl command so how is that working? — Nick Craig-Wood
– Nick Craig-Wood, Commented Apr 17, 2013 at 19:33
MoneyWorks allows an alternate URL scheme with the UN/PW embedded with the URL for direct cURL requests. ie. 1.2.3.4:6710/REST/user:[email protected]/params . Even so, when I leave the embeddd un/pw out of the cURL url I get "username/password required", which is to be expected. When using GO I get "404 Not Found". Something strange is going on, but at least I have it 100% working by passing the URL to cURL instead. I'll hack around with HTTP 1.0/1.1 and report back. — Darrrrrren
– Darrrrrren, Commented Apr 17, 2013 at 19:52
In the end, what matters is the bytes on the wire. I would use Wireshark to capture the bytes sent by both. If the critical difference isn't immediately apparent, I'd send variations (with any of http.Client, curl, or nc) until I can flip one thing and make either behavior happen at will. Then look for how to change that behavior in Go. — Scott Lamb
– Scott Lamb, Commented Apr 18, 2013 at 15:34

Darrrrrren · Accepted Answer · 2013-06-26 19:28:31Z

3

The issue was unicode-related. There was a %2F in my command (not displayed in my original question) that Go was converting to / that should have been left as %2F (cURL was properly leaving it as %2F). Changing the %2F to %252F fixed the issue.

It also appears that when creating a new HTTP request Go will parse your unicode back to plain text, so if you have %3D in the URL you submit to the HTTP request initializer it will convert it to =. I thought an obvious solution would be to put %253D into the URL but apparently there is a bug in Go that will convert %3D to = but NOT %25 to %. I had to use the Opaque URL request (request.Url.Opaque) to get around this.

edited Jun 26, 2013 at 19:28

answered Jun 26, 2013 at 14:23

Darrrrrren

6,1287 gold badges38 silver badges52 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Community · Accepted Answer · 2020-06-20 09:12:55Z

0

You say the curl command just works but if you have the latest curl(mine is 7.22.0). The request would be something like this:

curl url --verbose

GET / HTTP/1.1

User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3

Host: myhost.com

Accept: /

But you are setting req.Proto = "HTTP/1.0". Doesn't seem right.

edited Jun 20, 2020 at 9:12

CommunityBot

11 silver badge

answered May 18, 2013 at 6:27

Adnaan

1412 silver badges4 bronze badges

1 Comment

Darrrrrren Over a year ago

Yeah, the MoneyWorks documentation states that their REST API works best with HTTP/1.0... obviously this is contradicted by the command-line cURL request working just fine with 1.1. Either way, the GO code doesn't work with 1.0 or 1.1. I've just decided to pass an OS call to cURL for now.

Collectives™ on Stack Overflow

Golang HTTP GET request returning 404

2 Answers 2

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related