What's the neatest way to do this?

1. 2019-02-28 at 1:10 PM UTC

   #1
   

   Soyboy V: A Cat-Girl/Boy Under Every Bed African Astronaut [my no haunted nonbeing]
   Basically I need a client to be able to take a podcast RSS url, send it to a node backend to fetch and parse it, and return a JSON object.
   
   I can't just fetch the RSS XML file in the client because it keeps getting cockblocked by CORB.
   
   I'm thinking using a get and adding the url as params, but then the url looks ugly in the address bar.
   
   Maybe post, but then you can't just enter your own address easily.
2. 2019-02-28 at 1:33 PM UTC

   #2
   tee hee hee Naturally Camouflaged [slangily complete this slumberer]
   I've no clue. Sorry. 😦
3. 2019-02-28 at 5:33 PM UTC

   #3
   

   Soyboy V: A Cat-Girl/Boy Under Every Bed African Astronaut [my no haunted nonbeing]
   Thought about it, going to do it both ways and try to stick it on AWS lambda as a service. Once the CORS headers are set it should be accessible by the main app.
4. 2019-02-28 at 5:34 PM UTC

   #4
   

   Grylls Cum Looking Faggot [abrade this vocal tread-softly]
   yes i agree
5. 2019-03-01 at 9:55 PM UTC

   #5
   

   gadzooks Dark Matter [keratinize my mild-tasting blossoming]
   Whats an example podcast URL look like?
   
   Also, what do you want your JSON object to contain?
   
   Are you just trying to create a library of custom URL's pointing to podcast multimedia files? If so, what else besides a pointer URL do you need to store?