-
Notifications
You must be signed in to change notification settings - Fork 116
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
Link tag with invalid content (resulting on 404) must result in error? #157
Comments
I just ran into the same issue. One of my customers tried to request an invalid font (https://fonts.googleapis.com/css?family=Segoe) which returns a 400 error and throws an unhandled WebException. I'm going to submit a pr that handles webexceptions in LinkTagCssSource and adds to the InlineResult.Warnings collection: "PreMailer.Net is unable to fetch the requested URL: https://fonts.googleapis.com/css?family=Segoe" |
In case this was missed: #350 (comment) |
I need to process some HTML files out of my control, and sometimes I found itens like that
<link href='/test/mycss.css'>
but without origin or base tag to find the origin of request.How is the right way to ignore this and process the other content of my HTML?
And can we have an config to ignore 404 and remove this content on validate?
I try to create my own base URI to ignore all content but when I set the baseUri on PreMailer this removes the url getting only the base and give the same error.
Follow the simple test:
Follow the proposal who solve my issue (is valid?):
Thanks.
The text was updated successfully, but these errors were encountered: