Grount Connect Proxy: 404

I had a working grunt setup for several months and without changing anything on my side the proxy stuff stopped working. It might be due to some npm update updates or system (os x) updates, but somehow my proxy broke:

I have the following proxy log when making a request:

/web/app_dev.php/oauth/v2/token -> http://gambify.sites.dev:80/web/app_dev.php/oauth/v2/token

And this results in 404 not found. However, if I coil my request directly to http://gambify.sites.dev:80/web/app_dev.php/oauth/v2/token everything works fine, so my endpoint is actually there. And grunt also implements request and proxies at that location, but I still get 404.

Has anyone experienced something similar?

Best wishes, Mark

+3
gruntjs grunt-contrib-connect


source to share


No one has answered this question yet

See similar questions:

1
grunt forwarding connects to a different url

or similar:

1203
NPM vs. Bower vs. Browserify vs. Gulp vs. Grunt vs. Webpack
602
Difference between Grunt, NPM and Bower (package.json vs bower.json)
509
Rough watch error - Waiting ... Fatal error: see ENOSPC
302
Fatal error: Unable to find local grumbling
8
Grunt Connect Proxy: 404 Not Found
3
Specify headers with grunt-contrib-connect
2
Gruntfile.js with proxy error grunt-contrib-connect: ECONNRESET
1
Grunt connect proxy, handle subdomain handling
0
Generate sourcemap files with grunt-ts
0
Can't install npm package anymore



All Articles
Loading...
X
Show
Funny
Dev
Pics