-
Notifications
You must be signed in to change notification settings - Fork 56
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
What could cause an Error 413 on file convertion ? #32
Comments
UPDATE: I found out it could be linked to either the request :urn/metadata/:guid or the request GET :urn/metadata/:guid/properties. If this is the reason it may be because the metadata tree is too big (>20mb). That would not surprise me as it is a big model. I’ll try to see what I can do on my side to test that. … Unbelivable how I always start to find lead to solve my problems only when I ask other people to help me. |
I found out what was the problem. We were using |
Hi Kevin, thanks for reporting this 👍 Yes, the I think the converter could probably use the "chunked" download by default, so let me reopen this issue to track that. |
Hi Petr Glad to help. I only have a limited control on which Revit model I have access to but if you need it I may be able to do some test if you need it. |
Hello,
I have one file I cannot generate a gltf from. I get this error back when I try to:
Unable to generate the glTF file: abort(Error: Request failed with status code 413).
I wont be surprised if this come from the model complexity. It’s the metal part of a reinforced concrete section.
See below a lighter version of the model we managed to load.
(This generated glTF has ~250 item with ~75 metadata field attached to each)
I may be an isolated case but do you know what could trigger an error 413 during a model transformation ?
Could it trigger the Forge rate limit, or a quota, or something else I’m not aware of ?
Thank you.
The text was updated successfully, but these errors were encountered: