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
Instagram generates heaps of different referrer urls causing out of memory issues #15902
Comments
+1 to remove the |
Seems the but the
|
@sgiehl it looks like same might apply to facebook... eg
For these URLs we can remove the |
Also (also
Also below... not sure but this looks like it contains personal data... wonder if it makes sense to only store
Also maybe below convert to
Also from Google remove
Then also below could be shortend to maybe
Then below shorten to
These youtube urls remove
Could we also remove
from bing remove could remove the URL parameters
@sgiehl most important for now be the instagram and facebook URLs. We can also create a new issue for all the other ones. |
Maybe could also remove any configured |
Yes, that would be great. ideally we'd also need the feature from #15426 "Full" in case people really need this data for some reason (no BC break)? |
@tsteur can we close that one, or are there still some excludes open that should be added? |
Yes, thanks @sgiehl |
Seeing referrer urls like
It seems this
&e=
seems something unique to instagram as I see this in many different URLs. See also https://webmasters.stackexchange.com/a/114165The e parameter most likely stands for external or event. In the worst case this identifies a user and represents personal data?
We do not want to store this parameter in the DB and want to completely remove that string. Potentially we also want to move the
s
parameter. Not sure what it stands for.In some examples this might cause millions of different URLs causing millions of different rows when archiving.
The text was updated successfully, but these errors were encountered: