#fetchapi — Public Fediverse posts

TanStack Queryでいい。もう自分でやらなくていい。
https://qiita.com/nhatcaofedev/items/95f753e222480c5198e5?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #caching #React #Next_js #FetchAPI #Tanstack

TanStack Queryでいい。もう自分でやらなくていい。
https://qiita.com/nhatcaofedev/items/95f753e222480c5198e5?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #caching #React #Next_js #FetchAPI #Tanstack

Turns out, the easiest way to convert a "data:" URL to a JavaScript Blob object is not to split the URL into mime type, encoding, and data, and then, based on the encoding, do some wild atob() shenanigans

but instead

fetch(data_url).then(res => res.blob()).then(blob => …)

🙈 😂

#JavaScript #FetchAPI

Turns out, the easiest way to convert a "data:" URL to a JavaScript Blob object is not to split the URL into mime type, encoding, and data, and then, based on the encoding, do some wild atob() shenanigans

but instead

fetch(data_url).then(res => res.blob()).then(blob => …)

🙈 😂

#JavaScript #FetchAPI

Turns out, the easiest way to convert a "data:" URL to a JavaScript Blob object is not to split the URL into mime type, encoding, and data, and then, based on the encoding, do some wild atob() shenanigans

but instead

fetch(data_url).then(res => res.blob()).then(blob => …)

🙈 😂

#JavaScript #FetchAPI

Turns out, the easiest way to convert a "data:" URL to a JavaScript Blob object is not to split the URL into mime type, encoding, and data, and then, based on the encoding, do some wild atob() shenanigans

but instead

fetch(data_url).then(res => res.blob()).then(blob => …)

🙈 😂

#JavaScript #FetchAPI

Turns out, the easiest way to convert a "data:" URL to a JavaScript Blob object is not to split the URL into mime type, encoding, and data, and then, based on the encoding, do some wild atob() shenanigans

but instead

fetch(data_url).then(res => res.blob()).then(blob => …)

🙈 😂

#JavaScript #FetchAPI

#Development #Explorations
Forbidden request headers · Some request headers are more trustworthy than others https://ilo.im/16333j

_____
#Specification #HttpHeaders #Browser #JavaScript #FetchAPI #XMLHttpRequest #CloudflareWorker #WebDev #Frontend #Backend

#Development #Explorations
Forbidden request headers · Some request headers are more trustworthy than others https://ilo.im/16333j

_____
#Specification #HttpHeaders #Browser #JavaScript #FetchAPI #XMLHttpRequest #CloudflareWorker #WebDev #Frontend #Backend

#Development #Explorations
Forbidden request headers · Some request headers are more trustworthy than others https://ilo.im/16333j

_____
#Specification #HttpHeaders #Browser #JavaScript #FetchAPI #XMLHttpRequest #CloudflareWorker #WebDev #Frontend #Backend

#Development #Explorations
Forbidden request headers · Some request headers are more trustworthy than others https://ilo.im/16333j

_____
#Specification #HttpHeaders #Browser #JavaScript #FetchAPI #XMLHttpRequest #CloudflareWorker #WebDev #Frontend #Backend

I'm trying to track down a weird issue with using #streams as request body for #fetchapi requests in the #browser. After the first chunk is read, the connection stalls and the server never receives any data. It seems to be related to #http3 / #quic. When I downgrade the http reverse proxy to #http2, it works fine.

Has anyone experienced this too? Are streaming request bodies not compatible with http3? (as currently implemented in #chromium)

#javascript #http #chrome #webdev #nodejs

I'm trying to track down a weird issue with using #streams as request body for #fetchapi requests in the #browser. After the first chunk is read, the connection stalls and the server never receives any data. It seems to be related to #http3 / #quic. When I downgrade the http reverse proxy to #http2, it works fine.

Has anyone experienced this too? Are streaming request bodies not compatible with http3? (as currently implemented in #chromium)

#javascript #http #chrome #webdev #nodejs

I'm trying to track down a weird issue with using #streams as request body for #fetchapi requests in the #browser. After the first chunk is read, the connection stalls and the server never receives any data. It seems to be related to #http3 / #quic. When I downgrade the http reverse proxy to #http2, it works fine.

Has anyone experienced this too? Are streaming request bodies not compatible with http3? (as currently implemented in #chromium)

#javascript #http #chrome #webdev #nodejs

I'm trying to track down a weird issue with using #streams as request body for #fetchapi requests in the #browser. After the first chunk is read, the connection stalls and the server never receives any data. It seems to be related to #http3 / #quic. When I downgrade the http reverse proxy to #http2, it works fine.

Has anyone experienced this too? Are streaming request bodies not compatible with http3? (as currently implemented in #chromium)

#javascript #http #chrome #webdev #nodejs

I'm trying to track down a weird issue with using #streams as request body for #fetchapi requests in the #browser. After the first chunk is read, the connection stalls and the server never receives any data. It seems to be related to #http3 / #quic. When I downgrade the http reverse proxy to #http2, it works fine.

Has anyone experienced this too? Are streaming request bodies not compatible with http3? (as currently implemented in #chromium)

#javascript #http #chrome #webdev #nodejs

#DailyBloggingChallenge (61/100)

The #PetProject continues with a custom date picker instead of using a predefined component from #vue to learn more how the library is built.

Also chose to use the #fetchAPI over #axios, mainly because I am more familiar with the former. With this the app has HTTP access and converts the XML response from OSM to JSON.

#DailyBloggingChallenge (61/100)

The #PetProject continues with a custom date picker instead of using a predefined component from #vue to learn more how the library is built.

Also chose to use the #fetchAPI over #axios, mainly because I am more familiar with the former. With this the app has HTTP access and converts the XML response from OSM to JSON.

#DailyBloggingChallenge (61/100)

The #PetProject continues with a custom date picker instead of using a predefined component from #vue to learn more how the library is built.

Also chose to use the #fetchAPI over #axios, mainly because I am more familiar with the former. With this the app has HTTP access and converts the XML response from OSM to JSON.