Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

REST API with Single Page Application over HTTPS

  • 2 yanıt
  • 1 kişi bu sorunu yaşıyor
  • 1 gösterim
  • Son yanıtı yazan: krc_mtech

more options

Hi,

I am developing a web service using REST API. This REST API is running on port 6443 for HTTPS. Client is going to be a Single page application running on port 443 for HTTPS on same machine. The problem I am facing is:

While I hit the url say: https://mymachine.com/new_ui I get certificate exception for an invalid certificate because I use a self signed one, so mymachine.com:443 gets added to server exception. But still requests doen't go to REST API as they are running on https://mymachine.com:6443/restservice. If I manually add mymachine.com:6443 to server exception on firefox it works but it will not be the case in production for customers.

Some options that I thought are: 1. Give another pop up and ask to add REST server on port 6443 exception too.

   But this doesn't look proper as why an end user should accept the cerf for same domain twice.
   Also REST api server port can change. 

2. Can we programmatically add exception for domain and both the ports in one shot? Ofcourse with the consent of the user. 3. Use a reverse proxy. But then its going to have memory footprint on our system. Also it will be time consuming.

Please suggest some options. How do I deal with it. Thank you

Hi, I am developing a web service using REST API. This REST API is running on port 6443 for HTTPS. Client is going to be a Single page application running on port 443 for HTTPS on same machine. The problem I am facing is: While I hit the url say: https://mymachine.com/new_ui I get certificate exception for an invalid certificate because I use a self signed one, so mymachine.com:443 gets added to server exception. But still requests doen't go to REST API as they are running on https://mymachine.com:6443/restservice. If I manually add mymachine.com:6443 to server exception on firefox it works but it will not be the case in production for customers. Some options that I thought are: 1. Give another pop up and ask to add REST server on port 6443 exception too. But this doesn't look proper as why an end user should accept the cerf for same domain twice. Also REST api server port can change. 2. Can we programmatically add exception for domain and both the ports in one shot? Ofcourse with the consent of the user. 3. Use a reverse proxy. But then its going to have memory footprint on our system. Also it will be time consuming. Please suggest some options. How do I deal with it. Thank you

Tüm Yanıtlar (2)

more options

Hi, Firefox Volunteer Support is done by regular users ( well some not so regular ). No Developers will see what you are doing or asking. You will need to find the right places to discuss your issue such as github or stackoverflow.com/ maybe Starting by informing yourself.

Good Luck with it.

more options

Hi,

This problem is specific to Firefox only and so I asked it here. Thank you.