>
> The solution was to edit the '*onfetch(event)*' *function *in
> *service-worker.published.js* in the *Blazor WebAssembly Client "wwwroot"
> folder *and add a url exclusion for the /swagger folder.
>
Oh drats! I was hoping for something dead simple, but I'll see where it
leads -- *Greg*
Hi Greg--
I understand that you want the '/download/' URL to bypass the Webassembly
service-worker.
Server-side, I'd old-school a server-rewrite (mod-rewrite / IISRewrite /
custom HTTPFilter) or Fiddle the site config handlers. **sighs**
I found a SO article describing a deployment issue with es
Check.
On Mon, 22 Mar 2021 at 13:19, Greg Keogh wrote:
> My last 3 posts to this group bounced, and I notified David at Codify, but
> received no reply. Is the group active? -- *Greg Keogh*
>
--
Dan Cash
-m. 0411 468 779
-e. dan.c...@gmail.com
F.A.B. Information Systems Pty Ltd ABN 16 084
(UHF communication band established again)
I have a question about Blazor Webassembly app routing, but I think Blazor
uses the same routing logic as MVC (I think) so the question might be more
general.
Is there a way of configuring some routes to be ignored and passed on to be
processed as static
Working for me.?
On Mon, 22 Mar 2021 at 13:24, kirsten greed wrote:
> I see this but not the last 3
>
> On Mon, Mar 22, 2021 at 2:19 PM Greg Keogh wrote:
>
>> My last 3 posts to this group bounced, and I notified David at Codify,
>> but received no reply. Is the group active? -- *Greg Keogh*
>>
I see this but not the last 3
On Mon, Mar 22, 2021 at 2:19 PM Greg Keogh wrote:
> My last 3 posts to this group bounced, and I notified David at Codify, but
> received no reply. Is the group active? -- *Greg Keogh*
>
My last 3 posts to this group bounced, and I notified David at Codify, but
received no reply. Is the group active? -- *Greg Keogh*
