PoC using redirect

[joselsegura]

Description

Just a PoC for the smart-proxy service using HTTP redirects.

This solution doesn't cache anything, so the final smart-proxy will look very different from this implementation.

Fixes #15

Type of change

• New feature (non-breaking change which adds functionality)

Testing steps

Regular CI, no new tests at the moment

[codecov-commenter]

Codecov Report

Merging #16 into master will increase coverage by 0.90%.
The diff coverage is 23.61%.

@@            Coverage Diff             @@
##           master      #16      +/-   ##
==========================================
+ Coverage   19.40%   20.31%   +0.90%     
==========================================
  Files           9        9              
  Lines         438      507      +69     
==========================================
+ Hits           85      103      +18     
- Misses        341      391      +50     
- Partials       12       13       +1     

Impacted Files	Coverage Δ
server/errors.go	0.00% <0.00%> (ø)
server/server.go	20.00% <8.51%> (-9.34%)	⬇️
server/endpoints.go	60.00% <52.38%> (+17.14%)	⬆️
smart_proxy.go	30.15% <100.00%> (+1.12%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 61b1df1...c3f6ccc. Read the comment docs.

[tisnik]

LGTM, but the results will need to be handled correctly later

[Serhii1011010]

Looks good overall, I just don't like listing endpoints in each service, probably we could use prefixes, like

/api/v1/aggregator/* -> redirect to aggregator service
/api/v1/content/* -> redirect to content service

[natiiix]

LGTM, I don't see any significant issue 👍

[Serhii1011010]

btw, genericAggregatorRedirect, and genericContentServiceRedirect are almost the same function, so maybe it could be something like

func (server HTTPServer) redirectTo(baseURL string) func(http.ResponseWriter, *http.Request)

[joselsegura]

Done

[tisnik]

Looks good overall, I just don't like listing endpoints in each service, probably we could use prefixes, like

/api/v1/aggregator/* -> redirect to aggregator service
/api/v1/content/* -> redirect to content service

the whole redirect things are basically throwaway code anyway

[joselsegura]

I added a new function able to perform the request to the aggregator/content-service and then response back to the client