New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Way too many GET requests to the Micropub endpoint #85
Comments
At least one of these queries will be to check what post types to display on the homepage. At least one or two of these will then be checking what properties your post types support, so Micropublish can show all the properties that are relevant to edit. It used to be that That being said, I think Barry should be able to see if there's anything else in there |
I would expect only one call for |
Hmm, that's a bit too noisy. Jamie's right: config was getting too large to be stored in a cookie (#76) so Micropublish requests this from your endpoint when it needs it, but this is probably excessive. My alternative approach was to use something like Redis to cache the config response. I'll raise an issue and link it here. |
@hacdias Did you see this issue was fixed? It should mean there are many fewer requests to your server. |
@barryf it is much better, indeed! Thanks! |
Every time I do anything, Micropublish.net makes dozens of GET requests to my Micropub endpoint, until one returns 404 and then it proceeds normally. I'm not sure if this is an issue on my implementation or not.
If I open Micropublish.net, click on "Note", it happens. Quill and others do not have this behaviour.
This is the list of requests:
The text was updated successfully, but these errors were encountered: