When I inspect what their scraper sees, I get this:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html>
<head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head>
<body><p>{"code":8053,"message":"Invalid value 'bytes=0-524287' for 'Range' header. Invalid last byte position 524287","errorData":{}}</p></body>
</html>
Is there anything with the way that the server is handling partial content requests that could explain this?
To solve your problem, we need to add the ability to add custom meta tags. We will discuss it with the team and will inform you when we have an update on this.
@viktor.liablin thank you Viktor, this is business critical for us as we have multiple teams waiting on this being completed before they can complete a big project. Anything you can do to let me know expected timeframes would be very helpful.
I’ll be able to provide you with more information regarding the timeline once we’ve discussed this improvement with the team. In the meantime, you can indeed try using the approach of editing the index.html file.
If you have any questions or need assistance, feel free to ask.
@Alexander_Pavelko I haven’t been able to resolve this issue, I’m not sure it’s possible as the error is due to a partial content request and the range header.
Is this something that could be prioritised with paid consultancy from you guys? Like I said, it’s really critical for us to get it resolved.
We understand how this is important for you. I have raised a priority of this ticket to critical, we will see what we can do next Monday and will let you know here.
Thank you @Nikita_Fedorishchev - is there any way we could put custom meta tags on my instance faster than this? Could this be done as paid consultancy by your team?
You can modify the index.html file after each publishing because it always generates new content.
In order to keep these custom tags nearby the index.html file you can create the custom-tags.html file in the /ui-builder/containers/{CONTAINER_NAME}/custom-tags.html file and then when you publish the container the file will appear in the published folder
Thank you, I’ve added the custom tags as described but still get the same problem
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html>
<head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head>
<body><p>{"code":8053,"message":"Invalid value 'bytes=0-524287' for 'Range' header. Invalid last byte position 524287","errorData":{}}</p></body>
</html>
This seems to be a server side issue related to partial content requests using the range header. Are you sure that custom tags can fix this? Can the server configuration be changed instead?
a web browser can cache files for a while, the best way to load the latest version is open the browser dev tool and enable “disable cache” in the network tab
take a look at my test app, seems like it works, the forum displays its preview
