In order to automate this request by automated scripts, I constructed a simple-enough sr command by using some global variable values to be executed within my terminal to send a request to the gateway.

#$SOAPBOX_HOME/sr/sr -h $HOST_NAME -s $REQ_TOKEN_PORT -u $REQ_TOKEN_URL -f $OAUTH_TOKEN_REQ_FILE -a Content-Type:application/x-www-form-urlencoded $IS_SSL -J $ENC_TOKEN_OUT

I was however getting a 403 response back, not a HTTP 200 response code… urgh? After looking in the traffic monitor I noticed that it was failing on the credentials. OK, no problem, I will the request file (global variable = $OAUTH_TOKEN_REQ_FILE) that I created. This was the strange part because the credentials were correct.

This is weird because these came credentials works within SOAPBOX. Then I started to think more out of the box thought it might be the encoded-URL data values (changing ‘@’ to %40 and ‘&’ as %2D etc) so this was linear within SOAPBOX….Same issue! Even though I changed the values to encoded URL, the traffic monitor was picking up the correct and expected values that I was submitting.

I tried using the curl functionality within RHEL, (whist allows you to submit requests just like the SR utility though without the jargon of a browser) though I was still getting the same issue.

$CURL_HOME/curl http://$HOST_NAME:$REQ_TOKEN_PORT$REQ_TOKEN_URL -T $OAUTH_TOKEN_REQ_FILE -H Content-Type:application/x-www-form-urlencoded -k -o $ENC_TOKEN_OUT

By now I was clueless, this should work! I sat scratching myself on the possible issue though the penny dropped when I reviewed the trace logs of the issues. It seemed that there was gaps within the trace file, which was not showing up within traffic monitor. I found this was my only lead and investigated further.

I reviewed the request file I was using as the request body and there seemed to be an end of line character within the file when I submit a :set list command.

To avoid this, type :set noendofline binary and exit by saving the file. If you go back into the file, you will now notice a noeol value at the bottom of the terminal. If the ‘no end of line was introduced then the sr and the curl utility was able to send the requests.

References http://vim.wikia.com/wiki/Change_end-of-line_format_for_dos-mac-unix http://www.cs.sunysb.edu/documentation/curl/

About the author