You'd have a difficult time spoofing your IP address for a TCP connection (HTTPS).
Like the other the comment has suggested VPN's are a very effective way to to such a task...really any proxy system in general, TOR works as well. Hell, just have a friend leave a RaspberryPi in his house would work and tunnel TCP over SSH to it...
I'm going to use too many electrons informing you on the plethora of ways to spoof an IP address.
To me "spoofing" implies packet shaping.
I tried to find a good definitive difference between the two and couldn't find one. So as I said, could definitely be wrong.
In order to connect to a remote machine (in this case, a website) your computer must make a TCP connection to the remote server.
A TCP connection requires a three-way handshake to begin. This requires the sender (you) send a TCP SYN packet. If you "spoof" your IP address, the SYN ACK will never reach your machine, and you will therefore never be able to ACK back (with your "spoofed" IP). Because you never get this SYN ACK back with the servers initial sequence number, you will not be able to ACK back with the correct sequence number to even connect in the first place.
I'm fairly convinced you don't know how basic networking principals work, or at least do not know the difference between spoofing and proxying.