Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Ce site disposera de fonctionnalités limitées pendant que nous effectuons des opérations de maintenance en vue de vous proposer un meilleur service. Si un article ne règle pas votre problème et que vous souhaitez poser une question, notre communauté d’assistance est prête à vous répondre via @FirefoxSupport sur Twitter, et /r/firefox sur Reddit.

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Changing search engine in mobile app to engine that has authentication

  • Aucune réponse
  • 0 a ce problème
more options

Hello

I have a small niche non critical issue with setting my own search engine in the FF mobile app. Looks like it's doing a test to see if the URL is reachable, but gets rejected because of authentication.

It did not prompt for credentials, just immediately fails which prevented me from setting it.. Now I am self hosting a SearXNG search engine behind a reverse proxy (Nginx) with basic HTTP authentication, so I do have the power to disable it for a minute just to set the engine correctly and re-enabling it again.. After that, when trying to search for something after a session ends, it did prompt me for credentials and worked pretty well after that!

So see, this is very niche, but do prevented me from setting my own engine. It will be a show stopper for those who want to use such engine (with any authentication) but do not self host it...

Thanks a bunch Roy

Hello I have a small niche non critical issue with setting my own search engine in the FF mobile app. Looks like it's doing a test to see if the URL is reachable, but gets rejected because of authentication. It did not prompt for credentials, just immediately fails which prevented me from setting it.. Now I am self hosting a SearXNG search engine behind a reverse proxy (Nginx) with basic HTTP authentication, so I do have the power to disable it for a minute just to set the engine correctly and re-enabling it again.. After that, when trying to search for something after a session ends, it did prompt me for credentials and worked pretty well after that! So see, this is very niche, but do prevented me from setting my own engine. It will be a show stopper for those who want to use such engine (with any authentication) but do not self host it... Thanks a bunch Roy

Vous devez vous identifier avec votre compte pour répondre aux messages. Veuillez poser une nouvelle question, si vous n’avez pas encore de compte.