go-proxy | Write an intranet penetration tool in Go | Proxy library

I'm trying to get Go to use an internal enterprise Go-Proxy for module download - which requires an http_proxy to be accessible (enterprise firewall). However go get -u golang.org/x/lint/golint fails:

package golang.org/x/lint/golint: unrecognized import path "golang.org/x/lint/golint": https fetch: Get "https://golang.org/x/lint/golint?go-get=1": Forbidden

My setup:

• http_proxy and https_proxy environment variables are set
• no_proxy does not contain the IP or hostname of my Go-Proxy
• GOPROXY is set (go env -w GOPROXY=https://artifactory.mycompany.com/api/go/myrepo-go-virtual)

I checked:

• Using curl and directly querying the GOPROXY server works fine and I can download the file (so the https_proxy setting works)
• Counter-check with curl and explicitly unsetting http/https_proxy: No connection, as expected

Using tcpdump, I discovered that running go get seems to ignore my GOPROXY and ask my http_proxy to connect directly to the original url on golang.org (Options/sequence and ack numbers omitted for brevity), which the proxy/firewall blocks.

I have built an app on Django 2.0 and deployed to pythonanywhere.com. As Pythonanywhere.com hosting does not have SMTP server, I used external server (used hostiq.com SMPT server, where I have other websites hosted) to send messages using views. Everything worked fine, except the price :)

So I moved the app to reg.ru hosting (because it is cheap and has SMTP server). The web app works fine, except the links that send mails. All the veiws functions that use sending mails, fail and give an error "Incomplete response received from application". You can test it yourself by following the link: http://www.tajadventures.com/contact-us/

More information which may be useful to solve the problem:

1) I have two apps in a shared hosting reg.ru. 2) I use virtual environment on the server; 3) The Customer Support says that using PROXY (like this Working with django : Proxy setup ) is NOT ALLOWED in shared hosting. 4) This is what the log file says (sent by customer support):

To keep my project cleaner I decided (maybe wrongly) to split my one Django app into two. One app for the management of information, the other for display. And for this I thought using Django Proxy Models in the display App would be the best way. However, I've come across a problem with the ForeignKey fields within certain models and forcing those foreign keys to use a proxy-model, instead of its originating model.

Here's some examples to make it clearer:

App_1-model.py