
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Is there an existing issue for this?
Describe the bug
I have a Blazor Webassembly, .NET hosted application. On the server we host it on, the base path of the app will be
mydomain.com/coolapp
. Therefore, to try to get the app to render correctly on the server, I've been following Microsofts steps outlined in the "App base path" section of this page: https://docs.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/?view=aspnetcore-6.0&tabs=visual-studio#app-base-pathI'm following all the steps as I see there, but when I try to run the application, I'm getting 404's from blazor framework files. As far as I can tell, I'm doing everything described in the docs.
Expected Behavior
Following the steps as outlined in documentation should allow me to run my app locally, despite being configured to run at the
/coolapp
path when hosted on another server. Instead I get 404's from key files that are still hosted at the wrong path. Documentation is unclear whether I'm missing something.Steps To Reproduce
index.html
to:<base href="/coolapp/" />
Program.cs
:app.UsePathBase("/coolapp");
app.UseStaticFiles("/coolapp"); //without this, you get 404's from blazor.framework.js and nothing loads
"commandLineArgs": "--pathbase=/coolapp",
in the"BlazorApp1.Server"
profileFrom there, the app shows "An unhandled error has occurred. Reload" link, indicating that it has loaded some javascript. Inspecting the network tab in dev tools shows that the .dll files are 404ing.
If I navigate to this path directly it 404s, but if I remove the
/coolapp
from the url of the dll, it will download the file. So it's like it's still being hosted to the base path of/
rather than/coolapp
.What am I missing? I'm trying the most basic example possible. I pushed my code here for examination: https://github.com/DrLeh/BlazorAppNewBasePath
Exceptions (if any)
No response
.NET Version
6.0.101
Anything else?
Companion SO question: https://stackoverflow.com/questions/71113666/how-to-host-blazor-webassembly-app-with-different-base-path
The text was updated successfully, but these errors were encountered: