3 ms·
Are there still problems with GET requests not allowing very much data in the request? Will I have to send this as a POST, or is that all 200x?
by thomasahle 11y ago
Are there still problems with GET requests not allowing very much data in the request? Will I have to send this as a POST, or is that all 200x?
- paulhodge 11y agoAre you talking about the size limit (of about 2000 chars) on url strings? That's not a GraphQL thing, that's a limit imposed by certain browsers. If your request data might be bigger then it needs to be in a POST.
- thomasahle 11y ago> If your request data might be bigger then it needs to be in a POST. Ok. I was hoping things had gotten better.
- hhw3h 11y agoIf you look at facebook's Relay implementation the graphql queries are indeed sent as POSTs. https://github.com/facebook/relay/blob/master/src/network-layer/default/RelayDefaultNetworkLayer.js#L155 https://github.com/facebook/relay/blob/master/src/network-la...
- nathancahill 11y agoInteresting. I wonder how that plays with caching. Most caches ignore POST requests.
- tiglionabbit 11y agoYou don't want to use the browser's cache here. You can cache the properties in a more granular way yourself. Relay will do that for you.
- nathancahill 11y agoYeah, I guess I was thinking more about the server side.