Node.js TLSwrap.onread ECONNRESET - node.js

Question

So basically I have created my own "Imgur" where I enter a image URL etc.
https://images.hdsydsvenskan.se/980x588/Q2GO5t2lmKtW6WwGuEVQNTPmt4o.jpg
The issue is that it worked before but now I am getting errors (And I haven't change the code at all - My guess that it has to do with some URLS?) that are saying:
{ Error: read ECONNRESET
at TLSWrap.onread (net.js:622:25) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read'}
and honestly I don't see issue because it does work on other pictures but if I choose etc the one below. It keeps giving me that issue.
const fs = require('fs')
const path = require('path')
const request = require('request')
const express = require('express')
const app = express()
const PORT = process.env.PORT || 8888
// Path to images directory
const images = path.join(__dirname, 'images')
// JSON parsing middleware
app.use(express.json())
app.post('/newimage', (req, res) => {
const imageUrl = req.body.image_url
const imageName = req.body.image_name
request({
url: imageUrl,
headers: {
'User-Agent': 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36'
}
})
.on('error', (err) => {
console.log(err)
console.log(res.status())
res.status(500)
res.send('not ok')
})
.on('response', (response) => {
console.log(`Response for ${imageUrl}`)
console.log(response.statusCode + '\n')
res.send('ok')
})
.pipe(fs.createWriteStream(path.join(images, imageName + '.png')))
})
app.get('/images/:imagename', (req, res) => {
const imageName = req.params.imagename
const filePath = path.join(images, imageName + '.png')
console.log(imageName)
console.log(filePath)
if (fs.existsSync(filePath)) {
fs.createReadStream(filePath)
.pipe(res)
} else {
res.send('No image found')
}
})
app.listen(PORT, () => {
console.log(`Server listening on port ${PORT}`)
console.log(`http://xx.xxx.xx.xx:${PORT}`)
})
If anyone has any clue how I can solve it! I would appreciate it!

Answer 1

There's something funky going on with the Adidas-server that you mention in your comment, it requires a particular list of headers to be set before it works (requests time out for me otherwise):
request({
url: imageUrl,
headers: {
Accept: '*/*',
'Accept-Encoding': 'gzip, deflate',
Connection: 'keep-alive',
'User-Agent': 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36'
}
})
It looks like the Varnish cache that they're using might be misconfigured (or it's some strange attempt to try and block scrapers).