azavea / azavea/transit-analyst
Geocoding fails due to mixed content warnings
Open
bug
- Dominant language
- JavaScript
- Stars
- 11
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
From the browser console
> Blocked loading mixed active content “http://nominatim.openstreetmap.org/search?q=123%20Main%20St&limit=5&format=json&addressdetails=1&json_callback=_l_geocoder_0”
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the browser-console mixed-content warning while using geocoding for the example address, then locate the code that constructs the Nominatim request. Confirm the expected geocoding flow and whether results load; done means the request no longer triggers a mixed-content warning and geocoding works in the browser.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100